Codelite on Ubuntu

Discussion about CodeLite development process and patches
rajah
CodeLite Enthusiast
Posts: 30
Joined: Mon Aug 25, 2008 10:41 pm
Contact:

Codelite on Ubuntu

Post by rajah »

Hi Guys,

Have you guys tried Codelite on Ubuntu 64?
I downloaded the 32 bit and force installed it.
Install went fine and I installed libcurl3 as requested.

When I try to run Codelite I get the following

CodeLite: error while loading shared libraries:
libcurl-gnutls.so.4: cannot open shared object file: No such file or directory

The file is actually in /usr/lib

Any clues?

Rajah
User avatar
eranif
CodeLite Plugin
Posts: 6367
Joined: Wed Feb 06, 2008 9:29 pm
Genuine User: Yes
IDE Question: C++
Contact:

Re: Codelite on Ubuntu

Post by eranif »

My default machine i ubuntu 64 8.04.

There is a .deb package for Ubuntu 64 here:
http://downloads.sourceforge.net/codeli ... g_mirror=0
rajah wrote:libcurl-gnutls.so.4: cannot open shared object file: No such file or directory

I guess that you are using an old version of codelite - as a recommendation, use the latest development - they are always superior to the official release (which is based on revision 1789) they also goes through the same QA cycle so you can safe assure that you will get at least the same quality (in most cases, better quality)

Eran
Make sure you have read the HOW TO POST thread
rajah
CodeLite Enthusiast
Posts: 30
Joined: Mon Aug 25, 2008 10:41 pm
Contact:

Re: Codelite on Ubuntu

Post by rajah »

Yeah, 64 bit package worked fine. No problems.
Thanks as always for your prompt replies and solutions.
Rajah
eranif wrote:My default machine i ubuntu 64 8.04.

There is a .deb package for Ubuntu 64 here:
http://downloads.sourceforge.net/codeli ... g_mirror=0
rajah wrote:libcurl-gnutls.so.4: cannot open shared object file: No such file or directory

I guess that you are using an old version of codelite - as a recommendation, use the latest development - they are always superior to the official release (which is based on revision 1789) they also goes through the same QA cycle so you can safe assure that you will get at least the same quality (in most cases, better quality)

Eran
Post Reply