[CMake] OBJECT libraries and working around lake of target_link_libraries

We recently converted some software, comprising about 300 projects, to use OBJECT libraries from SHARED libraries so we could create "conveneince" libraries that were cominations of some of the 300 projects. Not being able to use target_link_libraries with thier transitive nature made this very

Re: [CMake] Non OBJECT libraries and population of $

cpp ...) > add_library(lib1 SHARED $) > > add_library(obj2 OBJECT c.cpp d.cpp ...) > add_library(lib2 SHARED $) > > add_library(combined SHARED $ $) > > Petr > > On 10 July 2017 at 19:41, David Hunter <davidhunte...@gmail.com> wrote: >> >> Currently y

[CMake] Non OBJECT libraries and population of $

Currently you can create an OBJECT library using "add_library( OBJECT ...)" this populates $ which can then later be used using something like "target_sources(name PUBLIC $)". I am wondering if there is some reason that $ can't be populated when you create a shared or static library, for

[CMake] Visual Studio 2010 default property sheets

Sorry if this a re-post had mail issue. I'm not sure if this has been discussed much within the CMake developer community but I wanted to give some thoughts on the use of Visual Sudio property sheets and some suggestion for CMake. As far as I know this is only relevant to Visual Studio 10 and

[CMake] Visual Studio 10 default property sheets

I'm not sure if this has been discussed much within the CMake developer community but I wanted to give some thoughts on the use of Visual Sudio property sheets and some suggestion for CMake. As far as I know this is only relevant to Visual Studio 10 and hence MSBuild. I am not familiar with older

[CMake] Managed C++/CLI, default build flags and configurations

Hi, I have a number of projects which contain mostly sub-directories with standard C++. I currently build all this stuff on Linux and Windows and everything is great. However I have a couple of directories in these projects which contain managed C++/CLI code so that I can expose the unmanaged C++

[CMake] Fwd: Bug fix requests for the *next* release of CMake...

I would second this, I have been manually removing the CMAKE_INTDIR by hand, I'm not sure why it's even there for C++ compiles. I prefer my compile lines as clean and simple as possible and I don't use this compile line define anywhere. If I want a compile line define to indicate what CMAKE_INT

[CMake] MIDL and Visual Studio 10 with |CMake 2.8.3

I have a project containing a few MIDL files that has been working fine using the Visual Studio 9 2008 generator. I have been migrating the project over to Visual Studio 2010 which includes using the cmake Visual Studio 10 generator. However the resultant Visual Studio 2010 files do not seems to