On Tue, 10 Jul 2018 at 09:57, J. Caleb Wherry <calebwhe...@gmail.com> wrote:
> Side note 1: Things like this eventually lead me to have a post process
(a python script) on all my VS project files to “fix” any issues like this.
It might interest you to know that I've worked around it a bit by tweaking
the IMPORT_PREFIX property:
set_target_properties(
${modname_dll}
PROPERTIES
OUTPUT_NAME
${module_name}
# Required to work around the fact that we rename our shared
libraries
# to have the same name as our static libraries, so when Visual
Studio's
# linker tries to create an export library, it clashes with an input
# library.
IMPORT_PREFIX
"import_"
)
Cheers,
Jason
--
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:
https://cmake.org/mailman/listinfo/cmake
