Linux Build

[killerbot]

This is probably already been asked a zillion times, but I just checked the wiki, and keeping in mind a post of Yiannis from yesterday :
what are the precise steps to build on linux.

Do you need to bootstrap or can you just call make ?
I also noticed configure.in is talking about rc2 and wx 2.4.2 --> ?? We use later versions, don't we ?


Lieven

[Ceniza]

The current method to build Code::Blocks under Linux is using bootstrap and then make, and using wxWidgets 2.6.x (2.4.x should work too).

[mandrav]

Bootstrap needs to be called only once, when checking out the sources.

(2.4.x should work too).

Nope, it does not. We 're using some wx2.6+ classes (like wxHashSet).

[killerbot]

This is what I have done (SUSE 10) :

My wx was probably already ok, from compiling an older pre svn version , so I did not do antyhing for that (now).

step 0 : get the sources through svn

step 1 : in the trunk (toplevel) directory : ./bootstrap 
             -> it said I should add the contents of /usr/share/local/libtool.m4 to aclocal.m4 ; I did NOT do that (how bas might this be)

step 2 : ./configure --prefix=/opt/codeblocks-svn

step 3 : make

step 4 : su

step 5 : make install

---> /opt/codeblocks-svn/bin  -> run codeblocks

==============> it WORKS

Is it correct that this position, is the output path of windows ?

What should I do know when sources change ? Can I build from within CB by using som cbp file ?
After doing such a thing, I just also do an update (it is not update.bat here ;-) ) ?

Are these assumptions correct ?

thanks,
Lieven

[mandrav]

This is what I have done (SUSE 10) :
...
==============> it WORKS

Congratulations . Who was saying it is difficult to build C::B in linux?

Is it correct that this position, is the output path of windows ?

What should I do know when sources change ?

Repeat steps 3-5.

Can I build from within CB by using som cbp file ?
After doing such a thing, I just also do an update (it is not update.bat here ;-) ) ?

Yes, you can use the CodeBlocks-unix.cbp to build C::B just like in windows. When you build it this way, you must run ./update (same like update.bat) and then use either output/run.sh or devel/run.sh to launch C::B.
After building it succesfully (i.e. have tested it works ok), I suggest uninstalling the autotools-built C::B (make uninstall) so that you 're not linking accidentally to the wrong libraries.