From: Miquel G. <gbm...@gm...> - 2010-11-03 12:38:27
|
2010/11/2 Knut Franke <Knu...@gm...>: > That's not exactly what the readme says. Is there a reason for the "make > clean" step? At least on Linux/GCC, it doesn't seem to make a difference > whether the files are compiled with "make" or "make staticlib"; but that might > be different on other platforms... That's the only reason. Other platforms may need the "make clean" step. > I don't see a big problem with depending on CMake (whether LabPlot/SciDAVis > depend on it or not), given that it's the build system of choice for KDE4 and > thus available virtually everywhere. Also, while my above point was invalid, > there's still the issue with the somewhat unintuitive build process for > opj2dat. Maybe that patch could include at least a suitable note in the > readme... What I dislike of CMake is: a) There is no easy way of removing the CMake generated files (like "make distclean" does for qmake), other that creating a "build" subdir and start cmake from there. That solution is (almost equivalent) to use a subdir for opj2dat. b) There is no easy way to see what the make command will do. The usual "make -n" command only shows a series of CMake related commands. Maybe in the long run handmade Makefile(s) will be the simplest solution. > If we do that, I'd suggest replacing >> +QT -= core gui > with > +CONFIG -= qt > which removes even more Qt-specific stuff. OK. > > Knut > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > Liborigin-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/liborigin-devel > |