[CMake] Question about best practices for large Multi-stage builds

I have the following build structure: workspace/ CMakeLists.txt # top level cmake component_a/ CMakeLists.txt # component cmake src/ # source in here component_b/ CMakeLists.txt # component cmake src/ # source in here Now, I'm trying to

Re: [CMake] Question about best practices for large Multi-stage builds

On Mon, Aug 26, 2013 at 12:16 PM, Thomas Taranowski t...@baringforge.com wrote: Now, I'm trying to implement a multi-stage build which does the following: 1) builds some external third-party dependencies. 2) auto-generate some code 3) build the source 4) package the result To do this, I'd

Re: [CMake] Question about best practices for large Multi-stage builds

On 2013-08-26 15:16, Thomas Taranowski wrote: I have the following build structure: workspace/ CMakeLists.txt # top level cmake component_a/ CMakeLists.txt # component cmake src/ # source in here component_b/ CMakeLists.txt # component cmake

Re: [CMake] Question about best practices for large Multi-stage builds

Dan, How did you end up handling the precompiled dependencies? Did you use a dependency management system, such as ivy, or roll your own system? Thomas Taranowski | 425-442-9209 | skype: thomas.taranowski | baringforge.com On Mon, Aug 26, 2013 at 12:21 PM, Dan Kegel d...@kegel.com wrote:

Re: [CMake] Question about best practices for large Multi-stage builds

Matthew, I tend to agree with you that 2 would not generally be a target. However, there are external factors at play that I haven't mentioned. For one, in our environment we'd like to pull the auto generated code into a code review tool, and to mechanize that we have a commit daemon running

Re: [CMake] Question about best practices for large Multi-stage builds

On 2013-08-26 16:37, Thomas Taranowski wrote: I tend to agree with you that 2 would not generally be a target. However, there are external factors at play that I haven't mentioned. For one, in our environment we'd like to pull the auto generated code into a code review tool, and to mechanize

Re: [CMake] Question about best practices for large Multi-stage builds

Thomas, there are a lot of parallels between your scenario and the one I just posted a question about yesterday (see subject line One build, multiple compilers and packages). One of the two scenarios that Matthew suggested is the one we've used to handle the external third party dependencies - we

Re: [CMake] Question about best practices for large Multi-stage builds

Craig, Thanks for the info. I went back and read through your post, and our build has many of the same issues you are facing. For our project I ended up keeping all dependencies in the context of the project workspace, and am not using the find* modules to fulfill dependencies. Thomas