Building of CodeLite itself from within the CL

[marfi]

Hi Eran,
I'm trying to improve wxWidgets project wizard from Gizmos but I cannot build the CL from CL... I use "Unix_Mac_Custom_Makefile" configuration with "Unix" configuration for "LiteEditor" project but a build process always fails with this error:

Code: Select all

../Interfaces/plugin.h:316: error: ‘PLUGINS_DIR’ was not declared in this scope

I have invoked Custom Build Target called "configure" as well. Please, how can I build CL from within the IDE? What workspace configuration should I use? I built the CL in this way several time before, but now it doesn't work..

Best regards
Michal

[eranif]

I am still building it this way...

'Unix_Mac_Custom_Makefile' is the correct workspace configuration, you dont need to change anything

This is a sample output from my compilation on ubuntu 64 bit:

Code: Select all

g++  -DON_64_BIT   -O3 -DREGEXP_UNICODE   -c Plugin/outputviewcontrolbar.cpp -fPIC -Wall -I/usr/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ -pthread -fno-strict-aliasing -DASTYLE_LIB -DYY_NEVER_INTERACTIVE=1 -DGTK -DSCI_LEXER -DLINK_LEXERS -D__WX__ -DINSTALL_DIR=\"/usr/share/codelite\" -DPLUGINS_DIR=\"/usr/lib/codelite\"  -ILiteEditor    -DPNG_NO_MMX_CODE -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/pixman-1   -I. -I./sdk/codelite_indexer/network -I./sdk/wxsqlite3/include -I./sdk/wxsqlite3/sqlite3/include -I./sdk/wxscintilla/include -I./sdk/wxscintilla/src/scintilla/include -I./sdk/wxpropgrid/include        -I./sdk/wxscintilla/src/scintilla/src -I./Interfaces -I./Debugger -I./Plugin -I./CodeLite  -o Release_gcc_unicode/outputviewcontrolbar.o

If you look closely, you can see that the compilation line includes -DPLUGINS_DIR=\"/usr/lib/codelite\"

Can you paste here the output you get from the build tab?
HINT: You can now use Ctrl-C from within the build tab
Eran

[marfi]

Oh, I see... The problem appears only if I try to build some specific sub-project or whole workspace. Build of "LiteEditor" project passed successfully. I have only one question: How can I make developed CL to load modified plugin from working copy and not from /usr/lib/codelite? I tried to add path to modified plugins directory to LD_LIBRARY_PATH variable, but it seems that the standard location has still higher priority...

Regards
Michal

[eranif]

Try running:

Code: Select all

./configure --plugins-dir=/home/eran/devl/codelite/Runtime/plugins

Ofc, replace /home/eran/devl/codelite/Runtime/plugins with your actual path...

Will generate a makefile where

Code: Select all

PLUGINS_DIR=\"/home/eran/devl/codelite/Runtime/plugins\"

Note that the codelite that will be created using this makefile, will not be able to load the debugger, since the debugger 'Runtime' directory is not exactly the same as /usr/lib/codelite

But you will be able to run codelite properly

Eran

[marfi]

Try running:

Code: Select all
./configure --plugins-dir=/home/eran/devl/codelite/Runtime/plugins

Ofc, replace /home/eran/devl/codelite/Runtime/plugins with your actual path...

Now it works, thank you!
M.

[DavidGH]

Hi,

To expand on this idea, my normal configure line for developing CL is:

Code: Select all

./configure --enable-debug --prefix=$(pwd)/CL-install --plugins-dir=$(pwd)/CL-install/lib

'make install' will then install the plugins to ./CL-install/lib, the debugger to /CL-install/lib/debuggers/ and the newly-built binary to ./CL-install/bin/codelite; everything else will also be in its correct 'local' location.

So you can run the new CL by ./CL-install/bin/codelite. There won't be any conflict with any other installation.

Regards,

David