make unistall
./configure
make
make install
sudo make unistall
./configure
make
sudo make install
Codesudo make unistall
make
sudo make install
Code: bashshould do it - and im not even totaly sure you need to uninstall beforehand (feel free to correct me!)sudo make unistall
./configure
make
sudo make install
one hour is quite a long build time in this case i think... what are your system specs?
also - once youve built once updating from svn should only get files that have changed, and make should only recompile files that have changed...
btw, depending on how new to ubuntu/linux you are
www.ubuntuguide.org (though for 5.04) has lots of handy info, and the offial wiki is crammed with helpfull info too
whats more there are a couple of handy apps such as easyubuntu(quite safe i tihnk) and automatix(heard complaints,mainly from people who tried to dist-upgrade after using this) that can install all sorts of goodness automaticly (such as a whole bunch of codecs, new ver of wine, java 1.5 etc)
QuoteCodesudo make unistall
make
sudo make install
This should do it. Note that you must uninstall first, or else when linking the app and plugins it uses the libcodeblocks.so previously installed (instead of the one you create with 'make'). Don't know why yet...
And, of course, don't forget that you can build it using codeblocks-unix.cbp ;)
After you build C::B succesfully once using 'configure' and install it, you can build C::B using itself. So everything will be like in windows world (run 'update' afterwards, etc).
# Gets rid of all created files
make distclean
svn up
# These two are just to make sure I catch any changes to these files
./bootstrap
./configure --prefix=/home/myusername/Apps/codeblocks-svn
make
make install
Code# Gets rid of all created files
make distclean
svn up
# These two are just to make sure I catch any changes to these files
./bootstrap
./configure --prefix=/home/myusername/Apps/codeblocks-svn
make
make install
I will test this though.If you're going to test it, just make sure to disable all plugins except the Compiler plugin (CodeCompletion esp. is known to make the build slower).
Make is currently the fastest build system and I doubt that codeblocks custom system is any faster.
I would doubt that, but feel free to test it and share your findings with us :)
By presuming that CB build system is slower than make I am not trying to insult codeblocks.
Are the auto make files inefficient, it does look like they throw a little more info at the compiler. Are the auto tools scripts use precompiled headers?
If you're going to test it, just make sure to disable all plugins except the Compiler plugin (CodeCompletion esp. is known to make the build slower).Your tips amaze me every day anew... :lol:
added "-O2 -ffast-math" in projectGood catch :)
C::B full rebuild (added "-O2 -ffast-math" in project to match make options):
If you're going to test it, just make sure to disable all plugins except the Compiler plugin (CodeCompletion esp. is known to make the build slower).Your tips amaze me every day anew... :lol:
Performance Tip: It is suggested to disable Code::Blocks code completion plugin, before opening the Ogre workspace. This workspace contains ~40 projects which will be parsed.
Well, they were measuring the time to compile Code::Blocks, not Ogre.
This particular project is parsed in well under 10 seconds on an average PC if you have all parsing options turned on (2-3 seconds otherwise). After that, code completion takes zero CPU and is entirely irrelevant.
If you either run a batch build or wait a moment before hitting the gear (which is usually the case anyway), the build takes the exact same time with or without that plugin.
If you are low on physical memory, then precompiled headers are the first thing you want to turn off.Good to know, trough I had preffer to disable the plugin rather than disabling precomp headers.
While precompiling the SDK, gcc can easily eat up 350 megabytes of RAM.
Personally, I'd advise to get more RAM though, it's not like RAM is expensive these days. Every ElCheapo PC from a supermarket has a gigabyte these days.Look, Germany is currently the most cheap (western) country to buy electronic devices. Most things are even more cheap than in USA.
You can get 1GB Kingston PC3200 DDR400 at newegg for $77.55 US. You have to pay extra for shipping...Thanks, but here $77.55 US isn't the definition of "cheap".
http://www.newegg.com/Product/Product.asp?Item=N82E16820141307
Look, Germany is currently the most cheap (western) country to buy electronic devices. Most things are even more cheap than in USA.That proves that you have never been anywhere near Germany... :lol:
Compilers eat RAM like candy...It is a fact of life, but I hate it. :P
Compilers eat RAM like candy...It is a fact of life, but I hate it. :P
You're right, no money to go near Germany, but that's from articles I've read and comparisons about electronic devices. Maybe it doesn't applies to computer devices, only electronic devices.Look, Germany is currently the most cheap (western) country to buy electronic devices. Most things are even more cheap than in USA.That proves that you have never been anywhere near Germany... :lol:
Hardware is at least 25% more expensive than in the USA.
For example a 512 MB 533 Mhz Kingston DDR2 ValueRAM DIMM costs 59-69 dollars in the USA.
In Germany, the exact same DIMM costs 69-89 Euros. 1 Euro = 1.2 dollars.
Nevertheless, if someone intends to develop software, that's a price one has to pay. You just can't do any serious development on a 128 MB machine, unless your project is entirely trivial.BTW, I have 512MB, but after all the MBs eaten by the shared video card, services (apache, mysql, etc), not a lot of ram is left.