• View
• Edit
• Upload
• History
• Print

BuildSystems

LyX Build Systems

LyX Build Systems

To make an educated guess on what might be the best build system for LyX we try to collect some facts on this page

Implemented features

Rate 0 (non-exitent) ... 5 (full support). Try not to use personal biased numbers but what you think a good consensus might look like. If you strongly oppose a certain rating, add an extra line and mark it as your personal opinion)

                     autotools       scons           cmake           qmake

[A] detection of     
external                 5             4               3               0
dependencies   

[B] create .rpm          5             0      

[C] create .tar.gz       5

[D] create .vcproj       0             2              5               5

[E] create window        0             5              0               
package

[F] completeness

[G] simplicity of        2             5              3               1
language for extensions

[H] PCH support          0.8*          0              0.8*

[I] Reliability          high          higher

[J} Supported           *nix,mac,      windows, *nix     mac,win/vc **
platforms              mingw,cygwin  (vc,mingw,cygwin)
...

* not reliable.
** other platforms are supposed to be supported

Measured performance (ratio to autotools, high numbers bad)

                     autotools       scons           cmake           qmake

[11] Empty build       1.0            1.0*             0.5              ?
(release mode)       

[12] Change one file   1.0            1.1/0.7**           0.35             ?   
(release mode)        

[13] Full build        1.0             ?               ?               ?
(release mode)


[21] Empty build       1.0             ?               ?               ?
(debug mode)       

[22] Change one file   1.0             ?               ?               ?   
(debug mode)        

[23] Full build        1.0             0.51            ?               ?
(debug mode, single thread, linux) 

[24] Full build         1.0            0.52
(parallel, 6 threads, linux)

* scons --implicit-deps-unchanged / make = 1.04. scons / make = 1.46. The former uses 
stored dependency, comparable to what make does.

** My test, adding an empty line to src/Buffer.cpp, yields scons/make = 0.69.

Weighting of items (numbers in a column should sum up to 100)

               developer1 developer2 developer3
[A]

[11]

[12]

[13]


[21]

[22]

[23]

Opinions

Abdel:

These are the very reason why I think CMake is superior: - XCode project for Mac - KDevelop project for KDE - GNU Makefiles for gcc - MSVC project for MSVC.

I only seldomly go to the command line to type CMake. With scons (and autotools) I had to do that all the time, which forced me to reload the project every time...

Bo:

> I chose scons for a lot of reasons, such as flexibility, platform > independence. I have doubt in cmake's approach because I am not sure > if cmake can achieve what we want. Conceptually, I am wondering: > > 1. Who is handling Package.cpp.in ==> Package.cpp? If cmake does it, > then the generated vcproject or xcode stuff can not detect changes in > Package.cpp.in. If cmakes gives this to make or vcproject, how can > cmake make sure these tools can do something like this? If cmake has > to re-generated a vcproject after such a change, why cmake is better > than autogen.sh? > > 2. Along the same line, will cmake be able to do 'cmake install > version_prefix=16', 'cmake install DESTDIR=destdir' in a platform > independent way? If vcproject does not do installation, how would > cmake do it, or trick vcproject do it? > > Overall, scons tries not to depend on another build system to achive > maximum power, and I am not sure how cmake can achieve the same.

Links

Related discussion threads:

• LyXDevelThread:92565

Categories

Category: Development, LyX_1_6