New CMake build scripts for DarkRadiant

[vlad]

I've just written CMake scripts to build DR under Linux.

 

I think CMake is more useful than Autotools.

These scripts make a 'standalone' build of DR, you don't need to install DR, for example, in /usr/local.

 

Here is the patch:

http://depositfiles....files/xb0fde4ei

 

Modified at 29 May 2010: Now you don't need to set LD_LIBRARY_PATH to run DR

 

How to build:

 

1. Make an empty build directory and chdir to it:

 

mkdir dr-build

cd dr-build

 

2. Run cmake and set your installation prefix:

 

cmake -DCMAKE_INSTALL_PREFIX=/home/vlad/dr_inst <darkradiant-source-root>

 

3. make install

 

4. enjoy;)

Edited May 29, 2010 by vlad

[PranQster]

Nice. That would make it a lot easier to deal with than installing it under /usr. At least once a year I do a full clean system install, usually with each major release of Mandrake. As such I format / and /usr when that happens. This will make (pun intended) for one less program to reinstall after doing so.

I prefer make to copy the files for installation so everything gets where it needs to go. I could manually copy everything to a directory in /home/me after running make, but I hate sorting through the source to get the files I really need.

[OrbWeaver]

I won't try to argue which is better out of Automake or CMake, since I have never used the latter, but I should point out it is perfectly possible to install DR into other locations using the --prefix argument to configure, e.g.

 

$ ./configure --prefix=/opt/darkradiant

[PranQster]

I suppose I knew that already, though I never tried using --prefix for my user's home path and doing make install as the regular user.

[vlad]

I won't try to argue which is better out of Automake or CMake

[/code]

 

As for me, there are some advantages:

1. It doesn't change the working copy; it doesn't generate files in working copy.

2. It compiles dm_editing plugin . Some months ago I tried to compile dm_editing, but there were some error messages.

3. Its syntax is simpler.

 

I should point out it is perfectly possible to install DR into other locations using the --prefix argument to configure, e.g.

$ ./configure --prefix=/opt/darkradiant

 

That's good! I didn't try it before, because I supposed that DR needs its libs and files to be located in directories like /usr/local/share etc. Now I confirm that it works with custom prefix, but why it doesn't compile dm_editing?

[OrbWeaver]

As for me, there are some advantages:

1. It doesn't change the working copy; it doesn't generate files in working copy.

 

So does automake, provided you write the scripts correctly (which I believe is the case for DR).

 

$ cd /tmp
$ mkdir dr-build
$ cd dr-build
$ /home/myself/darkradiant/configure --prefix=/opt/darkradiant
$ make

 

All build files will now be placed in /tmp/dr-build (i.e. the directory you are in when you run configure).

 

2. It compiles dm_editing plugin . Some months ago I tried to compile dm_editing, but there were some error messages.

 

It should compile dm_editing, but I haven't got round to fixing it all up so that it works. I should take another look at this soon.

 

3. Its syntax is simpler.

 

I won't argue with this, the M4 macro language isn't all that user-friendly.

[vlad]

So does automake, provided you write the scripts correctly (which I believe is the case for DR).

 

$ cd /tmp
$ mkdir dr-build
$ cd dr-build
$ /home/myself/darkradiant/configure --prefix=/opt/darkradiant
$ make

 

All build files will now be placed in /tmp/dr-build (i.e. the directory you are in when you run configure).

 

 

That's true, but I have to run autogen.sh before building DR. Otherwise, 'make' command doesn't work, it can't find some files.

This script modifies all Makefile.in, configure and other generated files.

[OrbWeaver]

That's true, but I have to run autogen.sh before building DR. Otherwise, 'make' command doesn't work, it can't find some files.

 

That shouldn't happen, it sounds like a bug in the build scripts. Can you post the exact error you get when you do this?

[vlad]

That shouldn't happen, it sounds like a bug in the build scripts. Can you post the exact error you get when you do this?

I don't think so.

I think that different versions of autotools aren't fully compatible with each other: they behave differently and make slightly different files.

 

I'll post this error tonight.

Edited May 28, 2010 by vlad

[OrbWeaver]

I think that different versions of autotools aren't fully compatible with each other: they behave differently and make slightly different files.

 

True, but this should only apply when generating the buildscripts with autoconf/automake. Once the scripts are generated, it should be possible to build on any platform using ./configure && make && make install without even having autotools installed.

[vlad]

True, but this should only apply when generating the buildscripts with autoconf/automake. Once the scripts are generated, it should be possible to build on any platform using ./configure && make && make install without even having autotools installed.

 

vlad@vladhome:~/aaa/gitrepos/dr-build> env LANG="C" make

CDPATH="${ZSH_VERSION+.}:" && cd ./../darkradiant/darkradiant && /bin/sh /home/vlad/aaa/gitrepos/darkradiant/darkradiant/missing --run aclocal-1.11 -I m4

aclocal-1.11: couldn't open directory `m4': No such file or directory

make: *** [../darkradiant/darkradiant/aclocal.m4] Error 1

[OrbWeaver]

Thanks, I noticed that m4 problem in previous build attempts. It should be fixed in the latest SVN revision.

[vlad]

Thanks, I noticed that m4 problem in previous build attempts. It should be fixed in the latest SVN revision.

 

Yes, it works!