the client is still experiencing linker issues such as: already defined in msvcrt.lib(MSVCR90.dll) errors
I know my static lib only exports 1 API. however,i have no idea really what the third party lib exports etc. they seem to be suggesting that my lib is exporting other common functions which is conflicting with their system and want me to only export my single API.
I am just not experienced enough to know if this is a configuration issue on their part OR i have to figure out exactly what I am exporting and limiting it somehow when i recompile my static.lib so it does not include those parts which are in common with their system. THus only utilize those parts of the third party lib that i need which is hard as i just link it and use it.
any help or direction in this matter would be apprecaited. i have this fully functional on my end but dont know what to do to make it work on their end. i read somewhere about .def files etc. just not sure what to do here. I have never really worked with .def files before either.
third party static lib into my static lib. my static lib has just one api that i let them use. i have no issues on my end but they have the following issues:
the clients response:
Specifically linking is failing due to the fact that the library is statically linking with many libraries common with the larger manufacturing tool chain build. These common library functions are being exported by the library causing the linking conflicts.
In order to resolve this problem the static library can only expose the functions associated with the one API itself in order to guarantee no linking conflicts result. Exported functions can be manipulated when the static library is built using a combination of linker options and module definition (.def file) statements.
the third party was simply stating : Integration of the static lib is failing due to linking errors. Example: ……xyz already defined in msvcrt.lib(MSVCR90.dll)
Edited by tazor2012, 07 September 2012 - 11:07 AM.