Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics

Dashboard
Notifications
Mark all as read
Q&A

How to do "out-of-source" build properly with cmake?

+3
−0

There are two broad types of build environments - in-source and out-of-source. "In-source" means the compiled files will appear in the same directory as source files. "Out-of-source" means there is a dedicated directory for compilation results. It seems the latter one is more suitable for large projects, and it is also recommended by cmake.

Suppose my project contains several libraries, which have their own cmake fiels, CMakeLists.txt.

I have two options - store build results for the libraries in the directories where libraries are, or in the directory of the project I am building.

project
    possible place to put build results for libA and libB
    project_1.cpp
    project_2.cpp
    libA
        possible place to put build results for libA
        libA_1.cpp
        libA_2.cpp
    libB
        possible place to put build results for libB
        libB_1.cpp
        libB_2.cpp

Is there an option which is preferred by cmake?

Are there any obscure considerations which make one or the other option preferable?

Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

0 comments

1 answer

+1
−0

Whenever I've worked with CMake-based projects, the structure has been something like this:

  • project
    • src <-------- typically this is a source control working directory
      • CMakeLists.txt
      • project_1.cpp
      • project_2.cpp
      • libA
        • libA.cmake
        • libA_1.cpp
        • libA_2.cpp
      • libB
        • libB.cmake
        • libB_1.cpp
        • libB_2.cpp
    • build <-------- CMake output goes here!
    • runCMake.sh

My runCMake.sh then looks like this:

#!/bin/sh
CMAKE= #wherever it's installed

BUILD=`pwd`/build
SRC=`pwd`/src

mkdir -p $BUILD
cd $BUILD

$CMAKE $DEBUG_OPTS $SRC

In other words, I have one build directory that stores the output of everything. Note that this directory serves to store three different types of things:

  1. CMake's own configuration files for this project (eg the CMakeCache).
  2. The project files that will be used by your build tool to actually build the software (eg Makefiles, or MSVC .sln and .proj files)
  3. The actual output of compiling and building.

I honestly don't know whether it is possible to store those three separately from each other and, if so, whether you can split up where the compilation output is stored. Nor, alternatively, how to split it up so that you have multiple build directories each of which stores those three things but only for a subset of your project (ie one for each library and one for your main application).

But I don't know why you'd want those things, either.

Why does this post require moderator attention?
You might want to add some details to your flag.

0 comments

Sign up to answer this question »