> Right now it looks like cmake does it. Yes. cmake re-generates the project file/make files when Package.cpp.in is changed, or a file is added. It is faster than autogen.sh and configure. The difference is that cmake is a 'two step' system, and scons is 'one-step' (and autotools is a 'three step' system).
> By definition, there is no platform independent installation, so I > wonder what exactly the requirements are here. (And of course I have no > clue how cmake manages it. But KDE uses cmake and runs on Windows and > is a bit more complex than LyX, so I doubt there's a problem) Abdel says cmake uses something calls cpack for installation. This makes cmake a 'three step' system. :-) > I guess more people are likely to agree on the opposite, namely that > e.g. a generated .vcproj file should be something that feels 'native' > when using in Visual Studio. I am old fashioned, and have not yet appreciated the convenience of a GUI. :-) (Also because I try to avoid MS products). > For running cl on the command line one does not need a .vcproj file. > [But I have still to see a scons generated .vcproj file to get an > impression how it works] It works as usually, just calls scons to build lyx, which is slower than the native nmake code that cmake generates. A sligh advantage is that if you change Package.cpp.in, there is no need to regenerate the project file. Bo
