Portable Codelite for Linux?

[whytea]

Is there a way to install Codelite on Linux (SuSE 64) without super user right?

Would be nice if it could be installed by just unpacking a tar file.

/Why Tea

[eranif]

Is there a way to install Codelite on Linux (SuSE 64) without super user right?

Would be nice if it could be installed by just unpacking a tar file.

/Why Tea

codelite depends on *many* shared objects - packing them all into a single tar file is just not the way to go (wxwidgets, gtk, cairo etc)

To install codelite without super user, you should build codelite as described here:
http://codelite.org/forum/viewtopic.php ... 1034#p4612
As the 4th step in the above linke, use this:

Code: Select all

cd codelite-src
./configure --prefix=/home/<user>/<somedirectory>
make
make install

This will install codelite under "/home/<user>/<somedirectory>"

Eran

[whytea]

Thanks for the reply.

Download the rpm source for SuSE, unpacked and copied to my Linux account and followed the procedure. Hit first hurdle,
No functional wx-config script was found in your PATH
Is the wxWidgets development package installed?

I know I need the wxWidgets, but I don't have root access to start with... I could resolve this and still get into other issues later. Is there an easy way to get around this maze?

/WT

[DavidGH]

Hi,

Download the rpm source for SuSE

The sourceforge tarball would have been easier. Are you thinking of building an rpm too?

I know I need the wxWidgets, but I don't have root access to start with...

That's a problem. The most elegant solution would have been to install the binary rpm to somewhere under ~, using the --prefix option. Unfortunately it doesn't work, as apparently the rpm isn't relocatable.
In any case, you will need the wxGTK devel files if you plan to use CodeLite to create apps that use wxWidgets.

The following should work, but it assumes that your system has installed the requirements to build wxGTK; that's mostly the gtk2-devel package. If that's not installed and you can't get someone to install it, I don't think you have any sensible workaround.

You will need to download and build wxGTK, but you can't install it to /usr/ or /usr/local as normal, so do the following:

Code: Select all

 tar -xzf ./wxGTK-2.8.12.tar.gz
 cd wxGTK-2.8.12
 mkdir build_gtk
 cd build_gtk
 ../configure --enable-unicode --prefix=$(pwd)
 make

(Optionally add --enable-debug to the configure line.)

This will build a 'local' wxGTK, designed to be used in-place, not 'make install'ed. This will work fine except that /full/path/to/build_gtk/wx-config isn't in your $PATH; so to use it, you somehow have arrange for it to be found. If building in a terminal, you can either use the full filepath or, easier, first do:
PATH=/full/path/to/build_gtk:$PATH
(When building a project using CodeLite, you will need to do one of those things in the project's compiler and linker options.)

You should then be able to build CodeLite without problems, assuming there aren't any other missing dependencies.

Regards,

David

[whytea]

Thanks David. Unfortunately that didn't work due to some dependencies.

In fact, I only want to use codelite a source browsing tool. Will it be possible to have a cut down version? This should simplify the build. I think this is my last chance

/WT

[DavidGH]

Will it be possible to have a cut down version?

No, and doing so wouldn't be likely to help anyway.

I think this is my last chance

No, your last chance is to install the same version of openSUSE on a computer where you do have root access. Then you can install whatever build dependencies that you need, and make a 'local' build of CodeLite installed to a path under ~. If you have the same username on both machines, you should then be able to make a tarball of the installation dir (and its subdirs, of course) and extract that in your target machine with a reasonable expectation that it will work.

That assumes that the target machine does have the wxWidgets runtime libs installed. If not, you can create a local install of wxWidgets and use it to create the CodeLite tarball. Then create a tarball of the wxWidgets libs and install them too into the corresponding location in the target machine.

If there are other runtime libs missing instead, then I don't think there's any reasonable solution.