Code::Blocks Forums
User forums => Help => Topic started by: mmccarty12 on January 24, 2012, 12:56:27 am
-
The following occur while trying to build SVN 7712(trunk) using the following configuration:
/configure --prefix=/scratch/mccarty/codeblocksSVN/trunk/build --with-contrib-plugins=all,-NassiShneiderman,-byogames,-spellchecker CC=gcc44 CXX=g++44
I also compiled the following version at obfuscated's suggestion. No errors occurred while compiling and installing.
The final code also ran, with some bugs, but it ran.
URL: http://svn.berlios.de/svnroot/repos/codeblocks/branches/wxpropgrid_debugger
Repository Root: http://svn.berlios.de/svnroot/repos/codeblocks
Repository UUID: 98b59c6a-2706-0410-b7d6-d2fa1a1880c9
Revision: 7712
Node Kind: directory
Schedule: normal
Last Changed Author: tpetrov
Last Changed Rev: 7712
Last Changed Date: 2012-01-22 19:36:42 -0500 (Sun, 22 Jan 2012)
make[2]: Entering directory `/scratch/mccarty/codeblocksSVN/trunk/build/src/scripts'
make[2]: *** No rule to make target `*.script', needed by `all-am'. Stop.
make[2]: Leaving directory `/scratch/mccarty/codeblocksSVN/trunk/build/src/scripts'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/scratch/mccarty/codeblocksSVN/trunk/build/src'
make: *** [all-recursive] Error 1
Although I compiled the same version from two different branches, it seems to me that this error should not occur, but what do I know.
Thanks for any help.
-
Hm, the broken commit is this one: http://svn.berlios.de/wsvn/codeblocks/?op=revision&rev=7711&peg=7711
Jens: Do you know the correct way to specify this rule?
-
Hm, the broken commit is this one: http://svn.berlios.de/wsvn/codeblocks/?op=revision&rev=7711&peg=7711
Jens: Do you know the correct way to specify this rule?
I guess there are several otherplaces, where the same issue occurs, if the build is not done from C::B's root-directory.
I will commit fixes for these issues during today.
-
Fixed in svn r7713 !
-
Jens:
Thank you.
Does this mean that we can build C::B out of the source tree?
If yes, what are the needed commands?
-
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).
-
Thanks for the explanation, this was what I was asking for.
-
jens and oBFusCATed,
Whatever you did worked for me. Thanks for taking the time to help.