I have a project where I currently have a dumb list of libraries to package
with the NSIS installer so the program will work under win32. It really
only works for one setup (currently Fedora mingw) with some prebuilt
libraries downloaded, others provided through Fedora, and others I build
myself. This is not very portable to say the least.

Is there an easy way when after find_library(...) or find_package(...) to
"collect" the appropriate libraries for the NSIS installer? Some of the
dependencies might be static libraries which I need to ignore, but the
others will be DLL's which I need to pull into the installer.

Thanks,
Richard
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Reply via email to