• View
• Edit
• History
• Print

Repositories11

This page gives links to the available binary packages for CodeLite 11.0 and its RAD plugin wxCrafter.

Note that the CodeLite packages now incorporate the required wxWidgets libraries (mostly wx3.1.0), so there is no need to install wxWidgets too. Of course you can if you wish, and you'll need to do so to build apps against wxWidgets. CodeLite doesn't (yet) require wx3.1 though, and you can still build your own against wx3.0.x if you prefer.

CodeLite apt repositories

To download CodeLite for Debian based systems (Debian / Mint / Ubuntu etc):

• Add the CodeLite public key to avoid warnings or worse from apt/aptitude

sudo apt-key adv --fetch-keys http://repos.codelite.org/CodeLite.asc

• Now let apt know that the repositories exist by adding the proper line from Table 1:
  • If you use an apt front-end e.g. synaptic, tell it to Add a repository, using as data the appropriate entry from the Table 1 below
  • If you do things by hand, add the appropriate URLs from Table 1 to /etc/apt/sources.list (you need to become superuser) :

 sudo apt-add-repository 'deb https://repos.codelite.org/ubuntu/ xenial universe'

Table 1: CodeLite repositories

• You then need update your repositories. In synaptic, click the Reload button. If you're doing things by hand, do:

 sudo apt-get update

• You should now be able to install CodeLite in the normal way through synaptic, or by doing:

 sudo apt-get install codelite wxcrafter

Official versus unofficial CodeLite packages

For a long time the official debian and ubuntu repositories supplied only the ancient CodeLite 6.1. However since ubuntu 16.04 (xenial) it has been updated to CodeLite 9.1 or later, and debian stretch has 10.0. This is very welcome, but creates a name-clash with any packages we supply. Therefore, starting with CodeLite 9.2, our debian packages have 'unofficial' added to the version e.g. codelite_10.0-1unofficial.xenial_amd64.deb. This allows you to select which to install using apt (or aptitude or synaptic).

Apt

You can see which versions are available by doing:

 apt-cache madison codelite

Then you can select which version to install. For example, to prefer the official 9.1 package use the line:

 sudo apt-get install codelite=9.1*

Synaptic

You can see which versions are available in the 'Versions' tab of Properties. Then use Package > Force Version followed by Apply. You may wish also to use Package > Lock Version.

CodeLite RPMs

There are rpms available for fedora 26 and 27 and openSUSE 42.3:

First tell rpm about the CodeLite public key. As superuser do:

 rpm --import https://repos.codelite.org/CodeLite.asc

Then either download the required rpm and install it as usual, or download and install in one step; e.g.

rpm -Uvh https://repos.codelite.org/rpms-11.0/fedora/codelite-11.0-1.fc27.x86_64.rpm

There are also source rpms for fedora and openSUSE. Note that these do not contain wxCrafter. To build binary rpms containing wxCrafter, you'll need to download the appropriate wxCrafter.so, plus the file wxgui.zip that contains its bitmaps, and put both in the rpmbuild/SOURCES dir before you build.

ArchLinux

CodeLite is available on ArchLinux via their AUR repository

To install codelite:

yaourt -S codelite

Previous CodeLite releases

See this page for links to packages from previous CodeLite and wxCrafter releases.

wxCrafter binary packages

The above packages supply the CodeLite IDE. Also available is wxCrafter, its gui-designer plugin. There are wxCrafter packages, labelled 2.8, here for the unofficial CodeLite packages. However there are few changes from 2.7, so I have not built for the official CodeLite 10 packages. Instead you should continue to use the wxCrafter 2.7 ones.

There are 32 and 64 bit packages here for: debian stretch; ubuntu xenial, zesty and artful; for fedora 26 and 27; and for openSUSE 42.3. Apart from artful and zesty, they are built against wxWidgets-3.1; so these unofficial ones will not work on earlier distro versions (though they might work if you build your own CodeLite against wx3.1...). Instead you can find older CodeLite/wxCrafter packages via the previous-releases pages.

Note that the official wxCrafter debs are not in the repo; use the direct links below.

In the following table I've provided direct links to the debian/ubuntu packages but these are more easily installed from the CodeLite repos in the usual way.

Download and install them with alongside CodeLite (it will do no harm to install wxCrafter without CodeLite, but it won't run!). Some of the debs are also available from the CodeLite repo (see above); the setup and public key are the same, but the packages are called 'wxcrafter'.

wxCrafter libs

What if you don't want to use a package, or there isn't one that your distro supports? If you want to build your own CodeLite (using wxWidgets 3.1), or are using the official xenial ones (which use wx3.0.2), here are the wxCrafter libs that the packages contain. Choose the nearest match, but there's no guarantee they will work on distant versions or different distros.

You will also need the file wxgui.zip that contains some of wxCrafter's bitmaps. This needs to end up inside the CodeLite 'share' installation (e.g. in /usr/share/codelite/). The wxCrafter.so itself needs to go in CodeLite's 'plugins' dir, which by default is probably /usr/lib/codelite/. How to do this? Well, you could just add them by hand as superuser. However there are other alternatives:

• If you are building from a tarball, 'configure' and 'make' as usual. Then before 'make install' add wxCrafter.so to Runtime/plugins/; it'll then be installed with the other plugin libs. There is no similar solution for wxgui.zip at present, but this might be fixed sometime...
• If you are building a CodeLite .deb package using the debian/rules from the repo, just add both wxCrafter.so and wxgui.zip to the same dir as the source tarball. 'rules' knows to look for them there.
• If you are using the fedora or openSUSE spec files to build an rpm, just add both wxCrafter.so and wxgui.zip to rpmbuild/SOURCES/. You can copy the .spec hack if you create a .spec for other distros.