Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
1
Using Code::Blocks / Re: Tools menu and Linux environment
« Last post by BlueHazzard on Yesterday at 11:39:12 pm »
So the big question is, is this expected behaviour from codeblocks or not? I mean, isn't codeblocks adding its own paths to LD_LIBRARY_PATH, and when we use them in the Tools menu start, could this interfere?
2
As gd_on said you should use libstdc++-6.dll from the bin folder of your MinGW installation (the one you used to compile your program). The one near CodeBlocks may be from another version of the compiler, it may work at first but can give you errors later.

Copy it to the folder containig your executable, you may need to copy others afterwards.
3
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?
4
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
5
I am new, I am here
6
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.
7
General (but related to Code::Blocks) / Re: C::B library name processing policy
« Last post by mirai on Yesterday at 08:11:08 am »
No, C::B is converting project settings to linker commands and the question is when and how does it convert provided library names.
8
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 .
9
Using Code::Blocks / Re: Tools menu and Linux environment
« Last post by cacb on November 26, 2021, 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
10
General (but related to Code::Blocks) / C::B library name processing policy
« Last post by mirai on November 26, 2021, 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?
Pages: [1] 2 3 4 5 6 ... 10