Code::Blocks Forums
User forums => Help => Topic started by: johne53 on January 07, 2008, 06:09:16 pm
-
I can dual-boot my PC between OpenSuse and 64studio (a Debian-based Linux distro). They're on separate partitions and I have a 3rd partition with the source code for C::B (this 3rd partition can be seen by both Linux distro's).
6 months ago I built C::B from source and installed it for my OpenSuse distro. But I never got around to doing the same for 64studio. Now I'd like to build & install C::B for 64studio but I can't for the life of me remember what I did to build it in the first place. Was there a makefile? Did I build it under Scons? I just can't remember.
Can someone please remind me what steps I need to go through and what libraries I'll need? I vaguely remember wxWidgets coming into the equation somewhere but I can't remember precisely.
Thanks,
John
P.S. Don't be confused about the '64' in 64studio. Both distros are 32-bit.
-
Look here
http://wiki.codeblocks.org/index.php?title=Installing_Code::Blocks_from_source_on_Linux
Tim S
-
Thanks Tim,
It all looks a bit more fearsome than I remember but I'll try it out tomorrow.... :)
-
On debian-based distros you should be able to install a package called "dpkg-dev" which includes "dpkg-buildpackage" a tool to build debian packages from special prepared source-trees.
The source trees have to include a subdir called debian.
C::B has got such a source-tree. So you can easily build .deb-packages by running "./bootstrap" and "dpkg-buildpackage" from the root-dir of the C::B-sources.
The original svn-sources lack some dependencies. to make them more portabel, but they might be broken on some debian-distros.
You can also download the sources from my repo. I fixed some dependencies to compile clean on the debian main-suites and to fix the binaries dependencies.
There are also some small patches included, that are not (yet) in svn.
If you use my sources you also need (at least) the dpatch-package.
If you have any questions about using the debian buildsystem with C::B feel free to ask. I will help if I can.
-
Thanks Jens - I got up early this morning to start the build. Then I saw the link in your signature which made me think there might be an easier way....
1) If I added your repositories to Synaptic would that enable me to install via Synaptic?
2) If so, would I still need to add your public key to apt's trustdb? (I've never fully understood the relationship between atp & synaptic).
3) I currently have wxGTK 2.8.4 installed (which Synaptic shows as the latest version). From last time, I vaguely remember that when I updated wxGTK something else stopped working so I'd like to stick with 2.8.4 - unless 2.8.7 is absolutely necessary.
-
Thanks Jens - I got up early this morning to start the build. Then I saw the link in your signature which made me think there might be an easier way....
1) If I added your repositories to Synaptic would that enable me to install via Synaptic?
2) If so, would I still need to add your public key to apt's trustdb? (I've never fully understood the relationship between atp & synaptic).
3) I currently have wxGTK 2.8.4 installed (which Synaptic shows as the latest version). From last time, I vaguely remember that when I updated wxGTK something else stopped working so I'd like to stick with 2.8.4 - unless 2.8.7 is absolutely necessary.
1) yes,
but
3) My packages depend on wxWidgets (wxGTK) >= 2.8.7 .
I have no problems using 2.8.7 on my system.
2)You can install packages without adding the public key, but synaptic will ask you if you really want that.
Synaptic is just a frontend/gui for the apt - suite.