External dependencies in Project are wrong?

[daniloz]

Since the update to rev. 7088, when the CodeBlocks.cbp project was changed, I get the following WARNING when I compile C::B :

Code Select Expand


WARNING: Target 'Code::Blocks - src': Unable to resolve 1 external dependencies: devel\libcodeblocks.a


And I get it for several other targets as well...

I could trace the problem to the included external depency for the targets as "devel\libcodeblocks.a", whereas it should be "devel\libcodeblocks.dll.a" on Windows systems, right?

[MortenMacFly]

whereas it should be "devel\libcodeblocks.dll.a" on Windows systems, right?

Yes. :oops:

It works for me as I have a patch applied that removes the .dll part for shared import libraries...

For the moment, please ignore. It'll work once I commit the patch.

[frithjofh]

I just reverted from last svn (I think it was 7121) to 7085 because of the same problems. So the bug is still around.

Regards and greetings from Asturias

frithjof

[codeur]

I just built trunk (svn 7406). Those warnings are there. A few of them are reproduced below

Code Select Expand

WARNING: Target 'Code::Blocks - Class wizard': Unable to resolve 1 external dependencies:
devel\libcodeblocks.a
WARNING: Target 'Code::Blocks - Default MIME handler': Unable to resolve 1 external dependencies:
devel\libcodeblocks.a
WARNING: Target 'Code::Blocks - Open files list': Unable to resolve 1 external dependencies:
devel\libcodeblocks.a
WARNING: Target 'Code::Blocks - Projects-workspaces importer': Unable to resolve 1 external dependencies:
devel\libcodeblocks.a
WARNING: Target 'Code::Blocks - Projects-workspaces importer': Unable to resolve 1 external dependencies:
devel\libcodeblocks.a
WARNING: Target 'Code::Blocks - Scripted wizard': Unable to resolve 1 external dependencies:
devel\libcodeblocks.a
WARNING: Target 'Code::Blocks - XP look & feel': Unable to resolve 1 external dependencies:
devel\libcodeblocks.a


[oBFusCATed]

Don't worry about them, btw it is even better this way.
If the external deps are set correctly there is too much relinking when something changes in the sdk...