Other ways to support Sylphis3D...
As so terribly obvious from the Subject, I'm trying to build a release of Sylphis from the source code. I've gotten as far as compiling the actual C++ from within VC2005 Express, but at this point, well...
I'm guessing that compiler.py and buildrel.py kind of package everything up for the release. First assumption. So, with that in mind, I run compiler.py, it executes just fine. However, when I then move on to buildrel.py, the first error I get is that it can't find sylphis.exe. Makes enough sense to me, sylphis.exe not being the same directory as the source and all. So, I back up to c:\sylphis_runtime\ (the folder VC2005 created when I compiled Sylphis' code), and copy and paste its contents into c:\sylphis\runtime\ (the base source directory)
Great. So I run buildrel.py again, and this time it gets a tad farther. This time I get an error about not being able to find "system/importer.pyc." Knowing a tad of Python, I go to system/importer.py and run it (which normally should generate the .pyc). Nopes. No error though, just no .pyc.
At this point, I'm basically stuck. Any ideas as to what I might be missing. (I don't want to file this as a bug report until I know I'm doing everything correctly.) Do I need the binary of Stackless Python installed, or will the stock install do just fine? Are there any Python libraries that need to be installed, like wxPython?
Thanks!
-=Derek
Building release
A release building should be this simple :
1) Compile sylphis.exe from the sources.
2) Copy sylphis.exe to the runtime/ folder (Skip this step if the latest SVN tree is used)
3) Copy sylphis.exe to the runtime/system/ folder
You should now run sylphis under the runtime/ folder. This is the release folder. The scripts you talk about in your posts are used to compile the .py files and copies then a different folder that you can later make a zip file. They provide an automated copy procedure and nothing more...