Topic: I am a programmer
QCS |
Posted at:
2010-12-12, 12:31 UTC+1.0
Compilation error: Please check if you have the correct GGZ libraries. KDevelop: Yes, the first import in KDevelop takes ages (especially on quite old computers like your's seems to be). That's normal (for KDevelop), please be patient. CMake is evil. ![]() ![]() |
ixprefect |
Posted at:
2010-12-12, 12:56 UTC+1.0
QCS: It would actually be nice if you could take a more detailed look into that, because even running cmake itself is surprisingly slow. From a quick glance, it seems that the cmake files use way too many regular expression calls. KDevelop uses Qt's regexp engine which seems to be somewhat slower than cmake's (no idea whether in general or just in our case), but I have a suspicion that so many regexes shouldn't be necessary in the first place. So if you could try to allocate some time at some point to look into where all these regexes are coming from, that would be great! ![]() ![]() |
QCS |
Posted at:
2010-12-12, 18:38 UTC+1.0
In fact our build system does three REGEX searches per .cc and .h file. Unfortunately CMAKE does not offer functionality along STRING(FIND ...) so I'll have to go with REGEXes here (using MATCHES). I'll try to do this with a few wild hackish replace-and-compare-result-to-origin actions and if it feels quicker, I'll push a branch for you to test. EDIT: bzr branch lp:~qcumber-some/widelands/cmake-without-regex It doesn't feel quicker for me, but YMMV. Maybe it's because I'm fairly recent with KDevelop and CMake.
Edited:
2010-12-13, 00:44 UTC+1.0
CMake is evil. ![]() ![]() |
bdfhjk Topic Opener |
Posted at:
2010-12-15, 10:00 UTC+1.0
I just compiled the source, the new version does not generate errors when compiling. ![]() ![]() |