Jens:
Thank you.
Does this mean that we can build C::B out of the source tree?
If yes, what are the needed commands?
I'm not sure, if I understood correctly what you mean.
Building from C::B's source-root works like always:
cd /path/to/codeblocks-source
./bootstrap (if any of the *.am-files or configure.in have changed)
./configure --prefix=/path/to/installation/dir/if/not/usr/local --<any_other_parameters_like_with-contrib-plugins=all>
make && make install
If you don't want to build from inside C::B's root-folder, what is a good idea in general (because you keep the source-tree clean of object and other build-files), you have to do some additional steps:
cd /path/to/codeblocks-source
./bootstrap (if any of the *.am-files or configure.in have changed)
mkdir -p /path/to/build-directory ( -p also creates missing parent-folders)
cd /path/to/build-directory
/path/to/codeblocks-source/configure --prefix=/path/to/installation/dir/if/not/usr/local --<any_other_parameters_like_with-contrib-plugins=all>
make && make install
The makefiles and all the intermediate build-files (object-files, *.la etc.) will be created below
/path/to/build-directory and do not litter the sources tree and can easily be removed with
rm -rf /path/to/build-directory/* .
In most cases the build-directory is created inside the root-folder of the sources, but this is not necessary.
After running the configure-script, neither the sources-tree, nor the build-folder should be moved to another place.
In most cases this is possible for the build-folder, but this is not guaranteed, because the absolute path to it is also stored inside the makefiles.
By the way:
the use of wildcards inside the
Makefile.am's might break the build, if other make-executables than gnu-make are used (but this only affects
make dist in our build-system as far as I know).
