Author Topic: Compiler path setting when codeblocks launch  (Read 1303 times)

Offline zetab

  • Multiple posting newcomer
  • *
  • Posts: 18
Compiler path setting when codeblocks launch
« on: May 12, 2022, 01:39:20 pm »
I am trying to setup a cross compiler (which is based on Cygwin) in codeblocks.
The compiler is working now and my project can be build successfully in codeblocks.
But when codeblocks launch, there's an error message about missing "cygwin1.dll".

The cross compiler executable and the "cygwin1.dll" are not in the same directory.
So I set the cygwin path in "Additional Paths" in the compiler setting and it works when building project.

If I add the cygwin path to the system's PATH variable, codeblocks will launch without error message.
But that may affect other applications.

I've done some test and found that codeblocs will run compiler's executable when launch but the "Additional Paths" setting is not applied.
Is this behavior by design? or it's a bug?

If it's by design, is there any other way to get rid of the error message without adding cygwin path to system's PATH?