You can file an enhancement request that the $<TARGET_OBJECTS> generator expression to be relaxed to include STATIC, SHARED, and MODULE libraries.
My suggestion is that a dummy source file to workaround the Xcode limitation on targets, is not as hacky as reverse engineering the object file locations. On Wed, Feb 27, 2019 at 9:06 AM Paul Smith <p...@mad-scientist.net> wrote: > > On Wed, 2019-02-27 at 08:39 -0500, Robert Maynard wrote: > > CMake only provides an official way to get the location of the object > > files for OBJECT targets ( $<TARGET_OBJECTS:objLib> ). For other > > target types the location is an implementation detail. > > Yes, but sometimes (as in my case) I need to know it :). I need to > examine the object files as part of my link processing. > > Exactly _because_ it's an implementation detail, it would be nice if > there were some way to retrieve it from CMake. I can file an > enhancement request if that seems appropriate. > > I could use an OBJECT target if it weren't for the Xcode restriction > that a STATIC or SHARED library must have at least one source file and > can't consist solely of an OBJECT library. > > I'm hopeful we can throw away our MacOS builds entirely but until that > happens... > > > Thanks for the reply Robert! > -- 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
