User forums > Using Code::Blocks

How to make a portable CB in linux?

(1/2) > >>

Loaden:
Hi, all, I am build CB use this bash script:

--- Quote ---./configure --prefix=/usr --with-contrib-plugins=all,-byogames,-Cccc,-cbkoders,-codesnippets,-copystrings,-envvars,-headerfixup,-libfinder,-NassiShneiderman,-exporter
make -j2
sudo make install
read -n1 -p "Press any key to continue..."
--- End quote ---
After build finished, I wonder how to make a portable CB?
In "make install" step, there have any options for portable?
Like this:

--- Quote ---make install --enable-portable --DESTDIR=~
--- End quote ---
Thanks!

MortenMacFly:

--- Quote from: Loaden on September 19, 2010, 02:57:03 am ---In "make install" step, there have any options for portable?

--- End quote ---
No. The best way to make C::B portable is NOT using automake for the build, but use C::B itself to compile C::B using the unix project file and then running the update script. This will create a run script which you can modify to make C::B "portable" by adjusting the CB_DATA_DIR (don't recall exactly the name of this environment variable atm...).

oBFusCATed:
Loaden you could use --prefix=/home/loaden/cb, then all files will be placed in that dir, and you can copy them around (not sure if will be portable)...
On linux, too few people care about the 'portable' thing, it is pretty windowsish...

Jenna:

--- Quote from: oBFusCATed on September 19, 2010, 09:11:22 pm ---Loaden you could use --prefix=/home/loaden/cb, then all files will be placed in that dir, and you can copy them around (not sure if will be portable)...
On linux, too few people care about the 'portable' thing, it is pretty windowsish...

--- End quote ---
On most linux system this will not work, because make install relinks the libraries with full path to avoid name conflicts.

Loaden:
I see, thanks a lot! :D

Navigation

[0] Message Index

[#] Next page