Linking static library into a .o-file instead of the executable

[chroot]

Hello

I'm not sure this is the right place to ask, hope it's not too far off.

I'm using a big external library in my project, but need it only in one class. I'd like to link the library into the .o-file.

I realise this is not how .o-files normally work, but it would be handy to realize it in this case. I would then only have to link to my own .o-file in every executable I need it, and not search the library every time.

Hope someone can give me a hint :-)

[weaknessforcats]

The build process requires the linker to search libraries to resolve reference4s in the .o files. The linker needs to produce an output so there really is no way for it to just link into your .o file and keep it a .o file.

A couple of questions:

1) Why the issue in the first place?? So you have library used in only one class, all that means is the link step is a little longer. Most IDE tools have the libraries searched in the order of the path list to the libraries. You could oput your library at the end of the list so it would be searched only once since other .o references would be resolved before the linker got to your library.

2) Have you considered making your .o file a library?? That way you could resolve the references and provide the linker with an output format. Your users would use your header and add your library to their builds.

[chroot]

Thank you for the fast reply

1) Mostly I'm trying to make things tidier, as there are already a lot of libraries that I have to link every time. It would work just putting the library at the end of the path, just fells overdone. I was wondering if there's a better way.

2) Yes, that's about what I'm trying to do. A library would be good, but when I create a library, are the libraries it uses linked into it? I thought I'd have to use my new library, plus the ones I'm already linking.

Or does this depend on the operating system?

[weaknessforcats]

Yes, a library already has its libraries linked into it. Your memory footprint would increase.

Personally, I would opt for the big link and not worry about it.