spt025 spt025 - 3 months ago 21
C++ Question

How to recompile source file every time while using cmake 2.8.2 in single build for c++11 and c++98 for shared library creation?

I have a project directory structure of:

Root
Source
Common
MyFolder
++ My 3 source files and header


When I am building my project it generates 3 to 4 shared libraries. Lib1 compiled using c++98 and others using c++11. Flags are added in CmakeList.txt which is at root.
I need my 3 source files to be compiled for Lib1 and for other Libs as as well. but here what happens is compiler is first compiling my source file for lib using c++11 and then it is trying to use same .o file for Lib1 as well. So for .o file which is generated using c++11 is throwing exception when same is used for c++98 compiled library.

So how do write this in CmakeList.txt such that compiler rather than trying to use same .o file will compile source file again for Lib1(c++98 compiled library)

Is there any flag I can specify so that it won't take precompiled .o file and will compile it again ?

Here flags are not being overridden for different shared libraries but actually same object file by make file is being used for different flags

Answer

This is sort of counter to how makefiles and cmake usually work.

Most users consider it really important that make performs an incremental build.

The usual way with makefiles is to do make clean which is supposed to remove any binaries and object files that were created.

However, sometimes I write cmake scripts that use globbing over the source directory to assemble the project. (That means, it says "just grab all *.cpp files in the /src folder and make an executable from them".) A makefile cannot check what files in a directory, so the make build will be broken after I add a new file, and make clean won't fix it -- the whole makefile will need to be regenerated by cmake.

Usually what I do is, I write a simple bash script, named rebuild.sh or something,

#!/bin/bash
rm -rf build
mkdir build
cd build
cmake ..
make -j3
./tests

And I put that in the root of my repository, and add /build to my .gitignore. I call that when I want to do a full rebuild -- it nukes the build directory, so its foolproof. When I want an incremental rebuild, I just type make again in the /build directory.

The rebuild.sh script can also serve a double purpose if you use travis-ci for continuous integration.

Comments