0

I am changing our build system in order to handle cross-compiling and packaging.

It is a common thing to ship dependencies' DLLs but CMake's FindXXX modules(./configure checks) don't provide the path to these DLLs but only to .a files. I quickly looked inside the .a libs and they all seem to contain the DLL's name.

What would be a proper way of extracting them[PS: The DLL file name of each .a] from the .a file on a Linux build machine?

epsy
  • 1
  • 1

1 Answers1

0

The .a file is the version of the library for static linking - if there is a dynamic linking version, it will be in the same location with the same name, except with a .so extension. (.so means "shared object").

caf
  • 233,326
  • 40
  • 323
  • 462
  • I am talking about .dll's. They come in two parts, the .dll itself and a .lib file(.a on linux when cross-compiled, apparently). The .lib/.a file is only used at linking time, while the .dll is only required at runtime. Sorry if I wasn't clear enough in the OP. – epsy Mar 21 '10 at 22:57