On Mon, Mar 24, 2008 at 8:29 PM, Jon A. Cruz <jon@...18...> wrote:
On Mar 24, 2008, at 2:30 PM, Joshua Blocher wrote:
Guys,
I'm current locked out of my sf.net account. As soon as i get back in i will commit what i have for cmake build system so far.
Joshua L. Blocher
Hi Josh,
I'm one of those people who is a little cautious about changing build systems (imake, scons, etc.). Do you think you can look at the problems Kai-Uwe had recently with cmake?
I'd hate to get most of the way done and find a killer problem at the last minute.
Below are my responses to the points he brought up. I also would hate to get caught at the last second.
I've looked at some of the generated makefiles and there biggest dependencies( other than what you really need to build) is guess what cmake. The ability to build makefiles without depending on itself would be nice, but it is also kind of pointless since you have to have cmake to build the makefiles to start with. Unless you intend to not distribute the Cmake build system files with whatever project you are working on. That would cripple building on whatever other systems that need projectfiles/makefiles built and most likely completely break building out of source. Cmake can be an automated configure script you can even rig it to ./configure script on *nix platforms. I'm not sure losing its Unix feeling is a good or a bad thing. As with anything how fast you can fix something in the system depends on how well you know it.
Yes, you do have to learn new syntax if you are build the system from scratch but for most developers its as simple as adding a file to a list. I would argue that this same with almost any build system not all tools and dependencies are in one place. Hmm, I will have to look into displaying default options or variables this more but I pretty sure its possible. I feel that it should configure itself to use all the available optional stuff automatically I easily trace wrong parameters to its source by going to the Cmakelists.txt at the effected files are in. Learning syntax is something you will have to do eventual but its far easier than auto* IMO
Yes you can grab any random ENV like this SET(pc_path "$ENV{PKG_CONFIG_PATH}") . As for the config.sit I don't know. There is a cmake file that adds support for uninstalling.
Joshua L. Blocher verbalshadow