Skip to content

Add export from buildtree#1

Merged
podsvirov merged 1 commit intopodsvirov:topic-cmake-project-5from
VestniK:topic-cmake-project-5
Jun 16, 2018
Merged

Add export from buildtree#1
podsvirov merged 1 commit intopodsvirov:topic-cmake-project-5from
VestniK:topic-cmake-project-5

Conversation

@VestniK
Copy link
Copy Markdown

@VestniK VestniK commented Apr 4, 2018

Allows to use library without installing it.

@podsvirov
Copy link
Copy Markdown
Owner

Hello @VestniK, thanks for PR and use case, but...
In my experience export(EXPORT...) is a generation time command. If we add asio via add_subdirectory the asio-targets.cmake file will not we available immediate and we could not link our targets to asio::standalone at first fime. What your think about this?

@VestniK
Copy link
Copy Markdown
Author

VestniK commented Apr 4, 2018

My main use case for build tree export is opening several project in one IDE session and make make them find each others build trees. It allows to build all projects at once and debug code across several projects. This setup is very flexible. I can open only few projects from the whole depndencies graph and get rest of them from the install trees.

@podsvirov podsvirov merged commit aabfd04 into podsvirov:topic-cmake-project-5 Jun 16, 2018
@podsvirov
Copy link
Copy Markdown
Owner

@VestniK, merged to target branch.
I also apply this idea to upstream PR chriskohlhoff#128.
Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants