Thread: Recovering Code::Blocks C++ linker settings

Hello, and thank you in advance.

For more than a year I have been working on a C++ console program by using Code::Blocks, in the Ubuntu Linux environment.

But today I noticed that the project's compiler and linker settings disappeared from the Project build options menu. The compiler option to enable C++0x is no longer checked, and in the linker options, the GSL libraries that I use (libgsl, libgslcblas, libm) are no longer listed in that menu.

However, when I rebuild and run the program, it works perfectly. It should not compile without the C++0x option because I use lambdas, and the program should not execute without the GSL libraries (all in the executable, not shared libraries.) I am sure I have rebuilt the program from scratch (in fact, I even manually deleted all the object files even though the "rebuild" option would take care of this.)

Is there a way I can restore the lost settings that I can no longer see? Since the program compiles and runs correctly, these settings must have been saved even if Code::Blocks crashed and erased some of these settings.

Many thanks for any suggestions!

Originally Posted by manasij7479

I think you should use a Makefile (or some build system to generate makefiles) to take care of these issues instead of relying on global IDE settings.
(Also, is your codeblocks project opened..or just the files ?)

I have used Code::Blocks to open the entire project, not just the source files. Despite the fact that the compiler and linker options are no longer visible, it appears that when I click "Rebuild Project", it is working flawlessly. Fortunately I had written down the names of the libraries and their paths in my notebook last year, and so I can rebuild the entire project if I have to, but I am surprised that the compiler and linker settings disappeared from the GUI menu.

I was considering using Makefiles also, but is there a good book that you recommend for Makefiles, to make sure that I acquire a deep knowledge so that can build and maintain big projects with this utility? At least Makefiles are very transparent and universal.

Also, can you recommend a truly nice editor that I can use with GUI functions like cut and paste, etc, instead of purely manual commands? I like the Code::Blocks because its GUI-based editor is very user-friendly and manageable in comparison the GVim that I have tried before. Even Ubuntu's GUI-Based GVim editor still requires a lot of manual commands. I don't mind learning more manual commands for a really good editor that is readable and intelligently indenting, with good colors to make syntax readable, but GVim is not very readable or user friendly (perhaps because I have not learned how to set it up well.)

Many thanks for the suggestions.

The Project Build options would not have disappeared. Some of them are simply not being displayed.

The Code::Blocks dialog/window (for the version I have installed on the current machine) has two sections: one section with the project name, and two subordinate build targets (typically targets like "Build" and "Release").

If you click on the project name, the right hand side of the window shows Compiler Settings, Linker Settings, etc (in separate tabs) that are common for all build targets (I typically enable manage warning levels here or support of dialects I want like C++0x, so get them whenever I build, regardless of which target I select). If you click on the individual Targets, the window will show options specific to each target. For example, it is common for "Debug" target to have an option set to include debugging symbol (which make the executable bigger, but help with stepping through the program when debuggin) while the "Release" target does not typically have that option set.

What happens if you click on the project name (as opposed to the "Debug" or "Release" targets) and THEN look at the linker options?

You're missing my point for a third time.

In that window with the "sub-pages" (actually called tabs) for compiler settings, linker settings, etc there is also a pane on the same window, to the left of the set of tabs. That pane will have three lines: one has your project name, then there are the targets (indented) i.e. "Debug" and "Release". Click on the project name, as well as the individual targets, and look at the settings you get.

Originally Posted by jimblumberg

Did you ever actually check any of those check boxes? By default all of those check boxes are empty. Once the boxes are checked and the project is saved they should be there the next time you open your project.

Jim

In the project's compiler options I had certainly checked the box that enables c++0x, and without C++0x the compiler must give an error message because I use lambdas in this project. I do remember the error messages when I forgot to check that box for C++0x in the compiler options last year.

And separately, the linker settings does not show the tree GSL library names that I have entered a long time ago. I do remember the error messages that I got last year when the linker settings were incorrect, and it took me some effort to enter the library names correctly.

But in any case, I have just rebuilt the entire project, and as we speak the new executable file (no shared libraries in this version) is running as usual.

Here is the picture. The code that you see in the editor uses GSL library functions, but the linker settings are empty in the Build options menu, for Debug, Release, or the project name itself. But despite this, the project can be rebuilt from scratch (rebuild option) and it executes normally.

FYI: The compiler settings are NOT under the Linker Settings tab!

Edit: You likely did the bad idea of entering the linker settings under the Global Compiler settings instead of the Project settings.

Edit2: http://wiki.codeblocks.org/index.php...files_exist.3F

Tim S.