User forums > General (but related to Code::Blocks)
A problem about C::B svn make(Ubuntu12.04)
cacb:
--- Quote from: jens on May 20, 2013, 09:05:23 pm ---Or just don't use our svn-repo, but the sources from my server:
http://apt.jenslody.de/testing/pool/main/c/codeblocks/
If you just download the *.orig.tar.gz tar-ball, you get the pure svn-sources without any patches, but after running ./bootstrap.
Ready for use with dpkg-buildpackage.
I update my repo much more frequently as this happens for the windows nightlies (currently I have svn r9099).
--- End quote ---
Thank you, jens. I didn't know there was a dependency between the scm client and the build system. That's a bit unfortunate. I shall have a look at those scripts, but downloading the *.orig.tar.gz post ./bootstrap tar-ball from your server, ready for or use with dpkg-buildpackage seems to be the easiest by far. Probably the download is much faster that way too.
Jenna:
--- Quote from: cacb on May 20, 2013, 09:30:00 pm ---I didn't know there was a dependency between the scm client and the build system. That's a bit unfortunate.
--- End quote ---
The build-system needs to know the svn-revision (at least for svn-builds, release builds are another story) and the only reliable way to get it, is to fetch the revision with the scm-client.
cacb:
Thanks again, I managed to build it properly from svn trunk, code fetched with bzr-svn with ./bootstrap + the manual steps you described in reply#19. The only issue I had was my local static wxWidgets build got in the way, causing the C::B dpkg-buildpackage to fail after some time. I solved that by "hiding" my local wx-config and "unhiding" after the dpkg-buildpackage, not sure if there is any smarter way but it worked
--- Code: ---sudo mv /usr/local/bin/wx-config /usr/local/bin/wx-config-hide
sudo dpkg-buildpackage
sudo mv /usr/local/bin/wx-config-hide /usr/local/bin/wx-config
--- End code ---
svn 9099 looks quite nice!
Jenna:
Run ./configure--help and you see the option --with-wx-config=CONFIG .
Add it (with path to correct wx-config) to DEB_CONFIGURE_EXTRA_FLAGS in debian/rules and it should work.
cacb:
--- Quote from: jens on May 21, 2013, 04:02:33 am ---Run ./configure--help and you see the option --with-wx-config=CONFIG .
Add it (with path to correct wx-config) to DEB_CONFIGURE_EXTRA_FLAGS in debian/rules and it should work.
--- End quote ---
Thanks yet again. I have tried this on another Kubuntu 13.04 (32bit this time) and successfully built the C::B debs from the tarball on your site. The way to configure which wx-config to use reminds me of a similar problem when using C::B and trying to tell C::B/compiler to find the correct wx-config during compilation. I have a compiler setting (other options) like this
--- Code: ---`/usr/local/bin/wx-config --version=2.8 --toolkit=gtk2 --cxxflags`
--- End code ---
As far as I know, hardcoding this way is the only way to select the correct wx-config within C::B. I would have liked to use a global variable, but at least in the past such variables didn't expand within backticks. Is there a smarter way now? Something similar to --with-wx-config=CONFIG with global variables would be nice to have. Or simply expand global variables also within backtick strings.
Finally, once the C::B debs have been built, they must be installed in the correct order. By trial and error I found that this worked (32bit version)
--- Code: ---sudo dpkg -i codeblocks-common_12.11svn9099_all.deb
sudo dpkg -i libcodeblocks0_12.11svn9099_i386.deb
sudo dpkg -i libwxsmithlib0_12.11svn9099_i386.deb
sudo dpkg -i codeblocks_12.11svn9099_i386.deb
sudo dpkg -i codeblocks-contrib-common_12.11svn9099_all.deb
sudo dpkg -i codeblocks-libwxcontrib0_12.11svn9099_i386.deb
sudo dpkg -i codeblocks-contrib_12.11svn9099_i386.deb
--- End code ---
Is there some easier way to simply say "install all and resolve dependencies between them" (without using a repository)?
Navigation
[0] Message Index
[*] Previous page
Go to full version