[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cmake
Subject:    [CMake] Best Practice to determine what type of libraries I am
From:       Mike Jackson <mike.jackson () imts ! us>
Date:       2008-06-27 14:16:38
Message-ID: 2C1F16C9-E28A-407E-813F-5CDB211DCCD4 () imts ! us
[Download RAW message or body]

What are the recommended ways to determine what type of libraries my  
application is linking against. An example should explain what I mean.

I use the HDF5 library as part of my project. It can be built either  
as a static or dynamic. If it is built as a static library then I  
don't need to copy it during the install phase. If it is built as a  
dynamic library then I _do_ need to copy it.

Would parsing the HDF5_LIBRARIES variable for a .lib or .dll work?  
Although not sure about that since you link against the .lib on  
windows but use the .dll? This is mainly for Visual Studio use.

Currently there is a #define HDF5_DLL_LIB defined in the H5config.h  
file. I thought of trying a simple try-compile a test file to see if  
it would compile and then base my decision on that.

Other ways? Better ways? Example code?

Thanks
-- 
Mike Jackson   Senior Research Engineer
Innovative Management & Technology Services



_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
[prev in list] [next in list] [prev in thread] [next in thread]