Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
1
I see the libstdc++-6.dll file in code blocks.  Is it possible to copy that file into my projects?  How would I link that to my projects so that I can go directly into command prompt and run the programs from there?
2
Yes I saw in the files that this question has been asked before.  The error message  states it cannot find libstdc++-6.dll.  In the process of using a utube video to work around this.  Release 20.03 rev 11983     Program is on c: \c++programs
3
I am new, I am here
4
The processing of library filenames is made in CompilerCommandGenerator::SetupOutputFilenames() at compilercommandgenerator.cpp:648.

Variable PrefixPolicy is loaded with the value in Project -> Properties -> Build targets -> Auto-generate filename prefix.
5
No, C::B is converting project settings to linker commands and the question is when and how does it convert provided library names.
6
You will need to lookup the linker documentation as C::B is an IDE and the linker does the linking not C::B.

The GNU linker docs are available at https://sourceware.org/binutils/docs/ld/  . The section you want is https://sourceware.org/binutils/docs/ld/Options.html . The two parameters you will be interested in are -l & -L .
7
Using Code::Blocks / Re: Tools menu and Linux environment
« Last post by cacb on Yesterday at 08:22:46 pm »
I solved the problem with loading *.so files.

Using ~/.bashrc to define LD_LIBRARY_PATH only works in a bash shell, so it is not the proper way to do it for all uses.

Instead, I made a file  /etc/ld.so.conf.d/myconfig.conf
and put a line in there defining the directory of my *.so files.

Then I did a
Code
sudo ldconfig

Now things worked as intended, the debuggers could find my *.so files
8
General (but related to Code::Blocks) / C::B library name processing policy
« Last post by mirai on Yesterday at 11:46:10 am »
Hi,

Please remind me what is the policy in C::B for conversion of linked static and dynamic libraries from "<path>lib<name>.<ext>" formulation to "<link_switch><name>"?
When C::B decides to convert "libsomelib.a" to "-Lsomelib" while passing such options to a linker and when to pass directly as defined in project options?
9
Using Code::Blocks / Re: Tools menu and Linux environment
« Last post by cacb on Yesterday at 06:59:01 am »
Tools menu,  I have disabled Tools+ long ago and I do not use it
10
Using Code::Blocks / Conditional code parsing / highlighting
« Last post by salem on Yesterday at 05:52:33 am »
Hi all,

I'm trying to figure out how to make C::B understand the contents of config.h (it does contain #define USE_PLUGINS 1) such that the conditional code in the picture (line 24) would be displayed normally.

If I manually add #define USE_PLUGINS 1 before the includes, the conditional code is no longer greyed out.

The project->properties has a "C/C++ parser options" tab, but that just talks about additional search paths.
Both files are in the project, and I added paths for both files to this dialog to no effect.

Do I need to do a build?
At the moment, I'm just using C::B to browse the code for the project.  It has it's own external CMake system going on, which I just run from the command line outside of C::B.

I'm using Release 20.03 rev 11997 (2020-03-28 13:56:24) gcc 9.3.0 Linux/unicode - 64 bit

Thanks,
Pages: [1] 2 3 4 5 6 ... 10