CodeLite IDE

Hey Eran is the main motive to build plugins via cmake that it's otherwise difficult/impossible to speficy -rpath correctly from the UI?

thx & cheers,

-- p

No...
There are three reasons for this:
1. If we want codelite to be included in the various Linux distros we need to provide a standard way of building codelite from the command line. And cmake is the best option (IMO)
2. We don't provide binaries for all Linux distros, so we need to provide a standard way of building codelite from the command line, again, cmake seems like the best tool for task
3. It provides an easy way to create packages on Linux

Eran

ok. I wasn't looking for a reason against cmake, just wondering why Windows plugins are built via the UI, but Unix aren't.

thx,

-- p

petah wrote:Windows plugins are built via the UI, but Unix aren't

On Windows its not common to use the command line.
When the transition to CMake was made, I played with the idea of changing the windows workspace as well to use CMake.
however, the FindwxWidgets module of cmake is not quite ready for Windows / MinGW the way codelite uses it (using wx-config)

So we left with the "old" way of building codelite on Windows

Eran

true it's not common but I miss it really bad even though I moved to Linux fairly recently. The default DOS/cmd32 window is terrible - your custom terminal looks great in comparison. I saw a long MSDN configuration about MS' C++11 compliance and the MS engineer only used the command-line with MSBuild.... strange.

cheers,

-- p