At some point in the 2.8 lifecycle, the choice was made to no longer copy the 
.pdb files on windows builds with the .lib that is generated.

I found a note somewhere, that there was "good" reasoning for it.. And in 
general, I agree, for many applications you don't need the pdb files for static 
libraries.

However, if the target of your project IS a static library that you supply to 
customers for integration into their toosl, you NEED to supply the pdb 
otherwise they are stuck getting the "pdb not found" warning message.

Is there any hope chance of bringing this back?

Scott
-- 

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://www.cmake.org/mailman/listinfo/cmake

Reply via email to