On Fr, 2016-06-10 at 10:41 -0400, Brad King wrote: > On 06/10/2016 10:28 AM, Tobias Hunger wrote: > > Any pointers on how to get to that information? Any example code that gets > > the > > artifact list? > > > > I do not think this information is particularly worthwhile to add, but am > > open > > to change this. > > An "artifactDirectory" field is not appropriate because there can be more > than one artifact per target, and in different directories. What is it > that an IDE might want to do with this information? If nothing, we could > just drop it for now.
I need the path to executables that get built as well as directories that libraries (dlls in windows) end up in, so that I can set up the environment for the executables in such a way that they find their libraries. > The cmGeneratorTarget::GetFullName method will give you the name of the > "main" file for a target. Passing `implib = true` will give the DLL > import library path on platforms where IsDLLPlatform returns true. I would have never found that! I'll change the code to list both the main artefact and the implib (if applicable). Best Regards, Tobias -- Tobias Hunger, Senior Software Engineer | The Qt Company The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho. Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B -- 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-developers
