Building the editor against WX
Posted: Thu Oct 12, 2006 02:49
Hi guys, I've had a horrible experience trying to build the editor and I want to see how we can make it easier.
First off, building CEGUI. Building its dependencies on Windows was not easy, this should be addressed and I don't think dependency packages should be the only solution, some documentation will help a lot, and I'm trying to do my part.
Second, building WX (again on Windows). I learned that it is extremely important to open the right solution file. One seemed more friendly for building the wx static libraries (used by the editor) than the other which is intended for building wx DLLs.
With the dependencies for the editor in place, I tried building. The compile went quite smoothely, but I am now stuck on a link problem. For some reason, the wxGrid's member functions are unresolved. This isn't a linker path problem, as I actually built the wx libraries one by one, and watch happily as the editor found each new wx lib. When all the wx libs were built, the editor still has unresolved symbols, so far just with the wxGrid class.
I had hoped to contribute a lot to the editor, but building it has really slowed me down, and now the project lead has decided to go with a competitor. I recommend having directions about how to compile the dependencies and the editor in a very easy to find place. You will most certainly receive more feedback once this is streamlined. I don't think I will have a chance to add the features I hoped to the editor, sorry about that. How about uploading a nightly build for various platforms that can be downloaded and tested immediately?
First off, building CEGUI. Building its dependencies on Windows was not easy, this should be addressed and I don't think dependency packages should be the only solution, some documentation will help a lot, and I'm trying to do my part.
Second, building WX (again on Windows). I learned that it is extremely important to open the right solution file. One seemed more friendly for building the wx static libraries (used by the editor) than the other which is intended for building wx DLLs.
With the dependencies for the editor in place, I tried building. The compile went quite smoothely, but I am now stuck on a link problem. For some reason, the wxGrid's member functions are unresolved. This isn't a linker path problem, as I actually built the wx libraries one by one, and watch happily as the editor found each new wx lib. When all the wx libs were built, the editor still has unresolved symbols, so far just with the wxGrid class.
I had hoped to contribute a lot to the editor, but building it has really slowed me down, and now the project lead has decided to go with a competitor. I recommend having directions about how to compile the dependencies and the editor in a very easy to find place. You will most certainly receive more feedback once this is streamlined. I don't think I will have a chance to add the features I hoped to the editor, sorry about that. How about uploading a nightly build for various platforms that can be downloaded and tested immediately?
