Bo Peng wrote: > Hi, Peter, > > I see development/cmake finally get in, and feel some competition now. :-)
Wasn't it called 'diversity' in an other thread? ;) > Anyway, your README.cmake seems to focus only on windows/msvc. Do you > have any plan to support other platforms? It would be good if you can > give some instruction on how to use cmake on, for example, linux > systems, so interested people can test it. It also builds with mingw and linux, and after bigger changes of the cmake files I will also test these builds again. I have not added gcc instructions because the main reason for the cmake files is the IDE support, and I don't wanna make it so clear, that it duplicates the auto/scons functionality. At ATM it only builds and you can't install anything with the cmake files. But I could add some instructions, no problem, they are nearly identical: make sure qmake 4 is in your path (on Linux I don't have to install my Qt4 build) and fire a 'cmake ..\trunk\development\cmake' in the build directory. It's also possible to generate kdevelop files (call 'cmake' to see the the generator name) but I haven't tested it. Would be nice if someone could give it a try. > Also, is win32/lyx.vcproj update to date? If not, can you update it > with your cmake generated one? It would be great if people can check > out lyx and compile it directly using this project file. Of course, > they need to install the supporting libraries. Seems win32/lyx.vcproj is totally outdated it uses src/frontent/qt2 files! I could try to update the file manually to the Qt4 build, but my cmake files don't help very much: cmakes builds for each source-subdirectory a vcproj file in an extra folder with absolute paths to the files and tools(moc/uic). We could add the zlib headers so you can at least build and run without the stuff provided by nls, aspell, and zlib. This was the way I gone when becoming familiar with lyx. Peter
