User forums > Using Code::Blocks

Filling in the Global Variable Editor

<< < (2/2)

PyTran++:
Thanks Jens for you reply. I am however not really certain yet about what I should do. I have attached a screenshot of the window with the fields I am trying to fill out. Could you supply me with what I need to fill out in the remaining empty fields (base and obj) and correct me if I have filled out some fields incorrectly. Thanks in advance

Jenna:

--- Quote from: PyTran++ on July 10, 2012, 11:50:00 pm ---Thanks Jens for you reply. I am however not really certain yet about what I should do. I have attached a screenshot of the window with the fields I am trying to fill out. Could you supply me with what I need to fill out in the remaining empty fields (base and obj) and correct me if I have filled out some fields incorrectly. Thanks in advance



--- End quote ---
Don't use the globa compile rvariables for the project (if you use the codeblocks-dev package, which includes a pkg-config file for C::B).
To verify, that the pkg-config file exists, just run pkg-config codeblocks --cflags from a console. It should output something like:
--- Code: ---$ pkg-config codeblocks --cflags
-I/usr/include/codeblocks -I/usr/include/codeblocks/tinyxml -I/usr/include/codeblocks/scripting/include -I/usr/include/codeblocks/scripting/bindings -I/usr/include/codeblocks/scripting/sqplus -I/usr/include/codeblocks/wxscintilla/include  
--- End code ---

If that's the case, you don't need the cb-variable.Just do all the changings I posted before in the projects "Build Options" (and the sources).

If you want to try it with the existing project-file, just use /usr as base and leave the objs empty.

You still have to make changes to the projects build options.
$(#cb)/include should become $(#cb.include)
$(#cb)/sdk/wxscintilla/include should become $(#cb.include)/wxscintilla/include
$(#cb)/devel should become $(#cb.lib)

And the cflags and lflags entries have to be surrounded by backticks ( "`").

PyTran++:
I tried your method but that did not do anything in my case. I might be missing something. However I managed to get something to work with the Global Variable Editor + the build option changes for the search tab. Unfortunately I am getting errors during the compilation of fortranproject.cpp. I have enlisted the Build messages below:

/usr/include/codeblocks/prep.h|18|warning: identifier ‘nullptr’ will become a keyword in C++0x [-Wc++0x-compat]|
/usr/include/codeblocks/prep.h||In member function ‘ID::operator void*() const’:|
/usr/include/codeblocks/prep.h|316|warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]|
/usr/include/codeblocks/prep.h|18|warning: identifier ‘nullptr’ will become a keyword in C++0x [-Wc++0x-compat]|
/usr/include/codeblocks/prep.h||In member function ‘ID::operator void*() const’:|
/usr/include/codeblocks/prep.h|316|warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]|
/usr/include/codeblocks/prep.h|18|warning: identifier ‘nullptr’ will become a keyword in C++0x [-Wc++0x-compat]|
/usr/include/codeblocks/prep.h||In member function ‘ID::operator void*() const’:|
/usr/include/codeblocks/prep.h|316|warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]|
/home/carlos/Downloads/fortranproject/fortranproject.cpp||In member function ‘virtual void FortranProject::OnAttach()’:|
/home/carlos/Downloads/fortranproject/fortranproject.cpp|169|error: ‘cbEVT_CLEAN_PROJECT_STARTED’ was not declared in this scope|
/home/carlos/Downloads/fortranproject/fortranproject.cpp|170|error: ‘cbEVT_CLEAN_WORKSPACE_STARTED’ was not declared in this scope|
/home/carlos/Downloads/fortranproject/fortranproject.cpp|175|error: ‘cbEVT_COMPLETE_CODE’ was not declared in this scope|
/home/carlos/Downloads/fortranproject/fortranproject.cpp|176|error: ‘cbEVT_SHOW_CALL_TIP’ was not declared in this scope|
/home/carlos/Downloads/fortranproject/fortranproject.cpp||In member function ‘void FortranProject::RegisterFileExtensions()’:|
/home/carlos/Downloads/fortranproject/fortranproject.cpp|1641|error: ‘class PluginManager’ has no member named ‘RegisterCCFileExts’|
||=== Build finished: 5 errors, 6 warnings ===|

Jenna:
You have to use a more recent C::B for the plugin in this case.

Navigation

[0] Message Index

[*] Previous page

Go to full version