User forums > Using Code::Blocks

does c::b include .so paths in linux but not .dll paths in windows?

(1/2) > >>

alle_meije:
In a workspace that I use in Linux I have 3 projects (let's call them A, B, and C). Project A and B are shared libraries and B depends on A, and project C is a program linked against A and B. Works like a dream, including 'build workspace', 'rebuild workspace' after which I can run the program from within c::b.

When I try to to the same in Windows, the program does not run because the .dll created from project B is missing.
(very likely if B was found the next problem would be project A's .dll -- that's in its own directory as well)

In Linux I did not externally set the library path to these project's directories and it just worked, but in Windows something extra seems to be needed. Is there a setting I can add so that it will still work if I move the workspace somewhere else? Perhaps in 'program arguments'? 

stahta01:
C::B adds the linker library search path to the PATH used.

Tim S.

oBFusCATed:
What fails - Build -> Run or running from the command line/windows explorer?

alle_meije:
It's the running that fails in Windows and not in Linux, with the same project files.
Building goes fine because I provide the compiler and linker search directories.

oBFusCATed:
You have not answered my question! So I repeat: what does fail:
1. Build -> Run
2. running from the command line
3. windows explorer
4. all of the above

Please answer with a number!

Navigation

[0] Message Index

[#] Next page