you could of course easily link against static libraries to avoid the problem (and make it easier for the people using the library later on). Apart from that the fact is simply that cmake would not automatically know where you have the DLLs to your library import files. So we would have to let the user specify another set of files he would like to copy to the binary folder. But it would be hard to check whether the DLL you specified really is the one for the library import file. So all in all you would not get total safety that way.
If you think it is a vital set of options to have, I don't mind adding it.
On May 15, 2012, at 12:18 AM, totte_karlsson wrote:
> I'm setting up a CMake project that links to an 'installed' libsbml distro.
> When I setup my CMake project, there is one question the user have to answer, in the CMake UI, which is the install folder for Libsbml. Using that info, the system get access to headers, libsbml link lib and the dll if building a shared version, + 3rd party dll's. However, the third party link libs, e.g. libxml2 are not installed by libsbml's CMake. Should it not be?
> Anything linking to libsbml's lib, will also need to link to the same 3rdpary shared (not if linked static) libs that libsbml itself was linked to, when built.
> Right now, I need to manually copy these link libs to the install location of libsbml, and I would rather not. Copying files around manually always end up in problems.. make sense?
> Also, it makes it hard to distribute a CMake project linking to libsbml since you have to motivate an end user to copy files around. But maybe I'm missing something...?
> Best Regards
> To manage your sbml-interoperability list subscription, visit
> For a web interface to the sbml-interoperability mailing list, visit
> For questions or feedback about the sbml-interoperability list,
> contact firstname.lastname@example.org
To manage your sbml-interoperability list subscription, visit
For a web interface to the sbml-interoperability mailing list, visit
For questions or feedback about the sbml-interoperability list,