Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • This is what I was trying to describe with my option #2. (Which may, indeed, be the best option.) But for big projects - and particularly for big components, depending on a lot of different targets scattered across the build tree and between lots of different directories - it seems to me that using custom commands and targets to organize binary products from all over the (quasi-opaque) binary build tree would be pretty cumbersome. (I'd say that's why install is a thing in the first place.) Commented Jul 25, 2016 at 8:11
  • How should make automagically know what of the different targets scattered across the build tree to choose from? It's your custom structure that makes a custom build process necessary. I don't think there's a way around that. Commented Oct 23, 2016 at 11:14
  • @null Of course, but that code is all generated by CMake and you don't have to touch it yourself. That's the whole point in using it in the first place. Commented Oct 23, 2016 at 22:12