Package Details: codelite 9.2-1

Git Clone URL: https://aur.archlinux.org/codelite.git (read-only)
Package Base: codelite
Description: Open-source, cross platform IDE for the C/C++ programming languages
Upstream URL: http://www.codelite.org/
Licenses: GPL
Submitter: None
Maintainer: uffe
Last Packager: uffe
Votes: 132
Popularity: 5.146856
First Submitted: 2008-08-01 09:11
Last Updated: 2016-07-29 18:10

Latest Comments

zerophase commented on 2016-07-30 16:45

I'm just referring to clang 3.8 as being a necessary dependency for building the ide. would it make sense to have clang as a makedepend?

uffe commented on 2016-07-30 11:56

Yes, if you have clang-3.5 installed - go into menu Settings -> Build settings...
In the dialog you can scan your computer for the compilers that you have installed.

Select the one you prefer..

zerophase commented on 2016-07-29 23:18

Does 9.2-1 compile with clang 3.5? On occasion I need to drop back to clang 3.5 for a custom Unreal build.

uffe commented on 2016-02-06 00:05

Updated to codelite 9.1.0

norby commented on 2015-10-27 15:41

Thanks, nickname!

I thought that this problem is resolved in the latest version, so I left out the comments.

P.S. Sorry for my bad English :(

nickname commented on 2015-10-26 17:25

Hi norby.
This happens (most probable) because of the lldb 3.7 version.

See the two different solutions uffe provides on the comments below

the other logs (mismatch) are displayed every time anyway

norby commented on 2015-10-26 17:16

The application fails to start:

Warning: Mismatch between the program and library build versions detected.
The library used 3.0 (wchar_t,compiler with C++ ABI 1008,wx containers,compatible with 2.8),
and your program used 3.0 (wchar_t,compiler with C++ ABI 1009,wx containers,compatible with 2.8)

uffe commented on 2015-10-23 08:43

bumped to 9.0

uffe commented on 2015-10-06 07:03

This worked for me - as a temporary workaround:

sudo chmod 000 /usr/lib/codelite/LLDBDebugger.so

nickname commented on 2015-10-06 06:01

Indeed. But I would have to re-compile it... (and it takes sometime)
If the problem persist it will be the only way out in the next release anyway so...

All comments