For some reason, Visual Studio 2003 is pulling in custom-action dependent libraries into the EXE.
Looking at the raw visual studio vcproj/sln, there are only 'project dependency' references, not "References" ... even then it doesn't even use the right path to the target.. but that could be due to VS breaking w/ 'external' build... Example of layout: libA executable custom action builds a header for executable based on libA's binary content visual studio adds in a project dependency of executable -> libA which makes perfect sense ... there is no libA referred in the linker libraries flags ... in the 'command line' specifier for compiling, it mentions a bad guess at where libA's import library is (seems to ignore the output path for it) Any ideas on how to work around this... moving from VS 2003 is currently not feasible... -- Thomas Harning Jr. _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
