-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've taken a look at cmake and it is really cool.
* easy to write * really really fast (forget scons) * handles libsuffix on x86_64 by default * module system * we can use modules from KDE4 project I've migrated lomoco to cmake on the weekend http://lomoco.linux-gamers.net/ Switch to cmake :) -- andreas Vadim Lebedev wrote: > Gianluca Sforna wrote: > >> On 8/11/06, Tanguy Krotoff <[EMAIL PROTECTED]> wrote: >> >>> Andreas Schneider wrote: >>> > Are you migrating to CMake now? >>> > >>> > Will WengoSCons die? >>> > >>> > I thought this is OpenWengo *open*, so it would be great if you would >>> > discuss changes, like using a new build system. >>> >>> It's 11pm here and I'm making some tests with cmake >>> WengoSCons/SCons is too slow and I start to like more and more cmake >>> while using it :) >>> >>> There is nothing definitive now, just investigations. But yeah maybe in >>> the near future WengoPhone will use cmake instead of SCons >>> >> >> Andreas is darned right here: this would be only the last case of >> "open"wengo embracing a new exciting and empowering technology without >> prioir notice to the community. >> Please note that, by embracing the FOSS way of doing software, you (at >> wengo) are not the only ones working on the code: I am sure many spent >> a considerable amount of time learning how to use/patch wengoscons to >> fit their (packaging) needs, so please consider discussing such a >> large change with the community _before_ even thinking what the >> replacement could be. >> Otherwise, that is a failproof recipe to upset (one or more) >> contributors. >> >> Now, I am not saying I love scons and the build system should stay >> this way forever ( I actually think that, given your repository >> organization, you should have been dropped it a looong time ago...), >> just that this kind of changes has to be discussed with all the >> parties involved. >> >> Cheers >> >> Gianluca >> _______________________________________________ >> Wengophone-devel mailing list >> [email protected] >> http://dev.openwengo.com/mailman/listinfo/wengophone-devel >> >> > Actually, > > I believe SCons is quite adequate for this task, > The problem that openwengo uses it in REALLY suboptimal way.... > In my own branch of wifo i've scrapped wengoscons and implemented much > lighter approach > and i've got 3-fold compile time boost... > > Another point i've mentioned long time ago: is suboptimal way to use QT > include file names, > in my tests i've was able to achieve 30%-70% compile time boost using > #include <Qxxx/Qyyy> scheme > > > > Still more, > The usage of static librarie:, it takes bigger memory and cpu budget > than dlls or object file collections. > > And the last point: I think the directory structure for the projecty > should be revamped, > > instead of > /src/model/componentX > src/presentation/componentX > src/control/componentX > / > it should be > /src/componentX/ > / > Each component should be made as a DLL > > This will create following benefits: > > 1) Shorter compile and link times > 2) Maybe possibility to test components separately, > which will significantly reduce debug times. > > > > > Thanks > Vadim > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Wengophone-devel mailing list > [email protected] > http://dev.openwengo.com/mailman/listinfo/wengophone-devel - -- http://www.cynapses.org/ - cybernetic synapses -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFE4F1Sf94+j/M+P8YRAoGUAKCwZMw9CSYSV+QYpJcNUoi+nJrDHgCgl2Xh xz9ZqurQzPJ6zdHiw4upKS0= =nytR -----END PGP SIGNATURE----- _______________________________________________ Wengophone-devel mailing list [email protected] http://dev.openwengo.com/mailman/listinfo/wengophone-devel
