Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Linker produces the wrong file extension

(1/2) > >>

pac:
When building a library and assignint to it the .lib extension

despite the builder log which says :

Linking static library: bin\Release\libmrf.lib
Process terminated with status 0 (0 minutes, 48 seconds)
0 errors, 0 warnings
 

the linker still produces the library with the .a extension.
Conseuauence : there is not libmrf.lib created but a libmrf.a is produced

is it a bug or am I missing something ?

Best regards

stahta01:
What compiler are you using?

.a is a minGW GCC library
.lib is a MS VC Library

Code::Blocks is a IDE it does NOT give extra abilities to the compiler.

Tim S

pac:
I am using Mingw tools

This is not about giving extra capabilities to the linker/compiler.
This is about giving it the argument specified in the text field Widget of the configuration dialog box.

THe Gnu Ld compler let you specify the file extension of  a dynamic library.

Example (which works perfectly with the command line):

g++ -o build/accelerators/libmrfaccelerators.lib -shared build/accelerators/Voxel.os build/accelerators/AccGrid.os build/accelerators/IVBase.os build/accelerators/IVVertexGrid.os

For static library you have the same feature because  the ar utility let you specify the extension too.


Best Regards

stahta01:
You do realize that just changing the extension to .lib does NOT make the output an MSVC compatible .lib.

If you wish to do this with code::blocks did you turn off.
"Auto Generate filename extension" and you most likely want to turnoff "Auto generate filename prefix"

Look for the above under "Project" -> "Properties" Tab "targets"

Tim S

pac:
arf...

Of course  I realize that and of course I tried to turnoff the options you're talking about
It does not produce the appropriate result (at least with  the nightly build of  the 24th January)

I think its a bug...


Pac

Navigation

[0] Message Index

[#] Next page