As a followup to my previous email dated 7/15/19, I learned from a
co-worker this week that if Project A's target_link_libraries() links
against an explicit path+filename of an external library, a subsequent
install(TARGETS ...) command will actually include that dependency in the
exported target
I'd like to discuss some shortcomings of CMake with regards to sharing
targets among projects. Other people have brought this up on this mailing
list in the past, but there has never been any useful feedback on it.
I'm going to refer to two projects:
- "Project A" produces some libraries
-
Using CMake 3.12.2.
Consider the following project:
project(myproject)
set(CMAKE_ARCHIVE_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/lib)
set(CMAKE_LIBRARY_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/lib)
set(CMAKE_RUNTIME_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/bin)
set(CMAKE_INSTALL_PREFIX
I believe it's possible to specify an "or" rule so that it would work with
either package. It should probably require the one it's built against
though, or at least prefer it if it works with both.
On Tue, Apr 9, 2019 at 12:32 PM Hahn, Steven E. via CMake
wrote:
> Would you consider updating
> wrote:
> > > Am Mittwoch, 3. April 2019, 22:26:59 CEST schrieb Benjamin Shadwick:
> > > > I tried cmake4eclipse, and it's a mixed bag. It requires a lot of
> > >
> > > tweaking
> > >
> > > Really? Just set _CMake Builder (portable)_ as the
On Wed, Apr 3, 2019 at 2:50 PM Martin Weber
wrote:
> To implement the 'index only files referenced through the build script'
> view,
> *any* IDE would have to *interpret* the build scripts.
> Just choose an IDE that has a build script interpreter to solve your use
> case.
>
Qt Creator and Visual
Oops, meant to send this to the mailing list, but GMail keeps trying to
divert me.
-- Forwarded message -
From: Benjamin Shadwick
Date: Wed, Apr 3, 2019 at 2:52 PM
Subject: Re: [CMake] Eclipse generator question
To: Martin Weber
On Wed, Apr 3, 2019 at 2:18 PM Martin Weber
advantage of what modern Eclipse versions can do.
On Wed, Apr 3, 2019 at 1:32 PM Martin Weber
wrote:
> Am Mittwoch, 3. April 2019, 18:44:04 CEST schrieb Benjamin Shadwick:
> > Update - I think I found a tolerable workaround:
> >
> > If I invoke cmake with -DCMAKE_ECLIPSE_GENE
my project-tweaking python script to add filters
to the generated Eclipse project to hide anything that isn't in the CMake
project.
On Wed, Apr 3, 2019 at 1:02 PM Martin Weber
wrote:
> Am Mittwoch, 3. April 2019, 18:44:04 CEST schrieb Benjamin Shadwick:
> > Update - I think I found a
he sources/headers belonging to each CMake target is not
really provided (although you can glean the sources part somewhat by
looking at the detailed target tree).
On Tue, Apr 2, 2019 at 9:04 AM Benjamin Shadwick
wrote:
> I've recently converted a complex C++ codebase to CMake. I'm stuck usi
I've recently converted a complex C++ codebase to CMake. I'm stuck using
2.8.12.2.
The codebase has a source tree, whose leaf directories each build a shared
library or an executable binary. The source lives in src/ while the headers
live in a separate tree under a sibling include/ directory.
11 matches
Mail list logo