User forums > Using Code::Blocks
Can't link object file from another project
Aleksandr:
I am also inclined to think that modern linkers have the possibility of such optimization. Well, or at least should have. But the use of the object file gives me 100% certainty. ;)
scarphin:
Why don't you just add the corresponding source files from the library sources to your project? Then you will have only the needed part of your library in your project.
MortenMacFly:
--- Quote from: MortenMacFly on June 17, 2014, 07:23:13 am ---Yes, its a bug.
--- End quote ---
Fixed in trunk.
Aleksandr:
--- Quote from: scarphin on June 17, 2014, 10:44:19 pm ---Why don't you just add the corresponding source files from the library sources to your project? Then you will have only the needed part of your library in your project.
--- End quote ---
As I wrote before, it does not need to compile. Why do the same job twice?
Well, your proposal is just another way. You can come up with some exotic such as symlinks or something more sophisticated. But ask a question. Why when linking, you think some objects as a given, and others as wrong? Are they bad or guilty? ;-)
--- Quote from: MortenMacFly on June 18, 2014, 08:41:19 am ---Fixed in trunk.
--- End quote ---
Does this mean that now you can add libraries to the project in two separate places? Will the confusion in this case?
oBFusCATed:
In fact this is interesting proposal. Add a library to a project and C::B will automatically link it:)
But no it is not implemented.
Morten has just fixed the feature where you add res/obj file and it just works!
You can add the object file manually in the other linker options, but I don't see how this is a problem or how this is confusing.
No one is forcing you to put anything there, but if you need to pass something special to the linker you can do it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version