On Fri, 2014-08-22 at 12:37 +0200, Nils Gladitz wrote:
> On 22.08.2014 02:15, Braden McDaniel wrote:
> > Ah. Bummer.
> >
> > Well, as you might have guessed, I'm trying to address an issue where
> > the LOCATION property of a target (EXPORT_TARGET, in the example above)
> > was being used. Is there some way I can get this information about the
> > target that doesn't involve modifying the CMakeLists.txt in each
> > subdirectory where a target of interest resides?
>
> Perhaps something like:
>
> file(GENERATE
> OUTPUT "${CMAKE_BINARY_DIR}/${LIB_PATHS}/${EXPORT_TARGET}_$<CONFIG>"
> CONTENT "$<TARGET_FILE:${EXPORT_TARGET}>"
> )
>
> Or if you want to keep this at build time a custom command with the
> OUTPUT signature and
> e.g. a custom target that depends on that output.
Actually, I'd rather not do it at build time; I just didn't realize I
could avoid it. That should work quite nicely. Thanks!
--
Braden McDaniel <bra...@endoframe.com>
--
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
