Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Changes for autotools builds planned
dmoore:
is it as simple as this?
http://ubuntuforums.org/showpost.php?p=2039057&postcount=16
(obviously someone needs to update for most recent changes)
darthdespotism:
You can install Codeblocks like this but when you do this you will be unable to remove CB again vie apt
a simple way to additionally achive this is by installing checkinstall (I don't need to say how to install this right?) and typing sudo checkinstall instead of sudo make install.
Note that you need to change the version number so it doesn't contain any whitespaces any longer. You can do this in the interactive phase of checkinstall, it's quite simple.
A more complex way to build codeblocks is by typing sudo dpkg-buildpackage -uc -us (-b -nc) instead of make and make install and installing the generated *.deb(s).
dpkg-buildpackage doesn't work for me with the new autotools-setup but I hop it soon will. checkinstall and make install may or may not work with this update, you'll simply have to try and eventually check out a older debian/ directory meanwhile
dmoore:
--- Quote from: darthdespotism on July 17, 2007, 05:14:12 pm ---You can install Codeblocks like this but when you do this you will be unable to remove CB again vie apt
a simple way to additionally achive this is by installing checkinstall (I don't need to say how to install this right?) and typing sudo checkinstall instead of sudo make install.
--- End quote ---
he suggested the checkinstall command line in his post (at the bottom)
--- Quote ---Note that you need to change the version number so it doesn't contain any whitespaces any longer. You can do this in the interactive phase of checkinstall, it's quite simple.
--- End quote ---
this is the sort of info I want in the wiki
--- Quote ---A more complex way to build codeblocks is by typing sudo dpkg-buildpackage -uc -us (-b -nc) instead of make and make install and installing the generated *.deb(s).
dpkg-buildpackage doesn't work for me with the new autotools-setup but I hop it soon will. checkinstall and make install may or may not work with this update, you'll simply have to try and eventually check out a older debian/ directory meanwhile
--- End quote ---
I coudn't get dpkg-buildpackage to work on the old autotool-setup either, but that might be because is i didn't specify the correct options (i.e. "-uc -us" or "-b -nc"). again this is info that belongs in the wiki.
thanks for the tips
darthdespotism:
without -uc -us dpkg will try to sign the package and as you don't have Mandrav's keys it will complain but did not stop building.
-b forces dpkg to only build a binary-Package and -nc prevents it from cleaning all the sourcetree. You probably want to clean it however (I don't do it because building everything takes considerably more time).
cstudent:
I use dpkg-buildpackage all the time, so I don't know why it won't work for you. If you posted some error message, I might be able to tell you what is going on. I have a old tutorial on my website on how to build the packages, but it is a bit outdated. A person of some intelligence, which I'm sure you all qualify, should be able to use the info and apply to building a new package. One of these days I'm going to update it and include how I'm using pbuilder now to build the packages. pbuilder starts with a clean and lean os in a chroot environment and then forces you to get the depends right. Anyway, I use dpkg-buildpackage -D -S -us -uc -rfakeroot to create a .dsc file which I then use to run 'sudo pbuilder build nameoffile.dsc' to build the packages. I was able to build the new separate packages this way. However, I did make some tweaks to the control file under the debian folder. I changed the build depends section to use c++ 4.1, wx 2.8.4 and added libgtk2.0-dev.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version