You want the [`execute_process`](https://cmake.org/cmake/help/latest/command/execute_process.html) command.


In your case, on Windows:

    execute_process(COMMAND CMD /c echo bar OUTPUT_VARIABLE FOO)


or on Linux, simply:

    execute_process(COMMAND echo bar OUTPUT_VARIABLE FOO)

&lt;br/&gt;
In this particular case, CMake offers a cross-platform solution.  CMake can itself be used to run commands that can be used on all systems, one of which is `echo`.  To do this, CMake should be passed the command line arg [`-E`](https://cmake.org/cmake/help/latest/manual/cmake.1.html#command-line-tool-mode).  For the full list of such commands, run `cmake -E help`

Inside a CMake script, the CMake executable is referred to by [`${CMAKE_COMMAND}`](https://cmake.org/cmake/help/latest/variable/CMAKE_COMMAND.html), so the script needs to do:

    execute_process(COMMAND ${CMAKE_COMMAND} -E echo bar OUTPUT_VARIABLE FOO)



I have a tabbed Actionbar/viewpager layout with three tabs say **A**, **B**, and **C**. In tab **C** tab(fragment),I am adding another fragment say fragment **D**. with

  
     DFragment f= new DFragment();
     ft.add(android.R.id.content, f, &quot;&quot;);
     ft.remove(CFragment.this);
     ft.addToBackStack(null);
     ft.commit();
               

I modify actionbar in DFragment&#39;s onResume to add up button:
	
    ActionBar ab = getActivity().getActionBar();
    ab.setNavigationMode(ActionBar.NAVIGATION_MODE_STANDARD);
    ab.setDisplayHomeAsUpEnabled(true);
    ab.setDisplayShowHomeEnabled(true);

Now in DFragment, when I press hardware(phone) Back button, I return to the original Tabbed(ABC) layout with CFragment selected. How can I achieve this functionality with actionbar up button?


actionbar up navigation with fragments

I used a cocoa static library in my application. When I compile my library I got the following error:

    Shell Script invocation error:can&#39;t open input file:
    /Users/sijuthomas/Library/Developer/Xcode/DerivedData/SCXML2-
        bbttehupryhijphhjdiemcytkvgy/Build/Products/Debug-iphonesimulator/
        libSCXMLParser.a (No such file or directory)
    Command /bin/sh failed with exit code 1

[![Screenshot for error][1]][1]

How can I fix this?


  [1]: http://i.stack.imgur.com/xAKI7.png

how to fix the issue &quot;Command /bin/sh failed with exit code 1&quot; in iphone

Is there a way to set a variable in a CMake script to the output of a shell command? 
Something like `SET(FOO COMMAND &quot;echo bar&quot;)` would come to mind

How do I initialize a CMake variable with the result of a shell command

<p>Is there a way to set a variable in a CMake script to the output of a shell command?
Something like <code>SET(FOO COMMAND "echo bar")</code> would come to mind</p>


In my CMake script I want to see if I have a file on my system, and if it is there do something with it, otherwise do something with a default file. Here is the code:

    find_file(
              ${project_name}_${customer}_config 
              ${ROOT}/configuration/${customer}/configuration.${project_name}.xml
    )

    if(NOT ${${project_name}_${customer}_config} STREQUAL
       ${project_name}_${customer}_config-NOTFOUND )
            configure_file(${ROOT}/configuration/${customer}/configuration.${project_name}.xml
                           ${CMAKE_CURRENT_BINARY_DIR}/conf/configuration.xml)
    else()
        configure_file(${FAPP_ROOT}/configuration/Default/configuration.${project_name}.xml
                       ${CMAKE_CURRENT_BINARY_DIR}/conf/configuration.xml)
    endif()

But it seems, this is not working. 

What is the proper way of checking if a file exists in CMake?

CMake check that a local file exists

I&#39;m using CMake with my project and set up a cdash server for continuous/nightly building. Everything works well and by setting up a crontab, we have hourly/nightly build/test results uploaded to our cdash server automatically.

My next step is to add test coverage report to the build. I find the document here http://www.cmake.org/Wiki/CTest:Coverage but frankly it&#39;s a bit far from a practical guide.

Currently I&#39;ve added the required flag (instead of `-fprofile-arcs -ftest-coverage`, I find `--coverage` better), the compilation process generates .gcno files. But then I&#39;m stuck. The command 

    make NightlyCoverage

doesn&#39;t seem to do anything. Could anybody tell me what is the next to do? The result that I want, is by doing `make NightlyCoverage`, coverage reports are generated and uploaded to cdash server.



Detailed guide on using gcov with CMake/CDash?

I&#39;ve got some config files (xml, ini, ...) in the `config` directory next to the source files. How can I copy all the files in the config directory into the build directory (next to the executable file) each time I make the project?

How to copy contents of a directory into build directory after make with CMake?

I am new to programming in general so I decided that I would start by making a simple vector class in C++.  However I would like to get in to good habits from the start rather than trying to modify my workflow later on.

I currently have only two files `vector3.hpp` and `vector3.cpp`. This project will slowly start to grow (making it much more of a general linear algebra library) as I become more familiar with everything, so I would like to adopt a &quot;standard&quot; project layout to make life easier later on.  So after looking around I have found two ways to go about organizing hpp and cpp files, the first being:


    project
    └── src
        ├── vector3.hpp
        └── vector3.cpp

and the second being:

    project
    ├── inc
    │   └── project
    │       └── vector3.hpp
    └── src
        └── vector3.cpp

Which would you recommend and why?

Secondly I would like to use the Google C++ Testing Framework for unit testing my code as it seems fairly easy to use. Do you suggest bundling this with my code, for example in a `inc/gtest` or `contrib/gtest` folder? If bundled, do you suggest using the `fuse_gtest_files.py` script to reduce the number or files, or leaving it as is?  If not bundled how is this dependency handled?

When it comes to writing tests, how are these generally organized?  I was thinking to have one cpp file for each class (`test_vector3.cpp` for example) but all compiled in to one binary so that they can all be run together easily?

Since the gtest library is generally build using cmake and make, I was thinking that it would make sense for my project to also be built like this?  If I decided to use the following project layout:

    ├── CMakeLists.txt
    ├── contrib
    │   └── gtest
    │       ├── gtest-all.cc
    │       └── gtest.h
    ├── docs
    │   └── Doxyfile
    ├── inc
    │   └── project
    │       └── vector3.cpp
    ├── src
    │   └── vector3.cpp
    └── test
        └── test_vector3.cpp

How would the `CMakeLists.txt` have to look so that it can either build just the library or the library and the tests?  Also I have seen quite a few projects that have a `build` and a `bin` directory.  Does the build happen in the build directory and then the binaries moved out in to the bin directory?  Would the binaries for the tests and the library live in the same place? Or would it make more sense to structure it as follows:

    test
    ├── bin
    ├── build
    └── src
        └── test_vector3.cpp

I would also like to use doxygen to document my code.  Is it possible to get this to automatically run with cmake and make?

Sorry for so many questions, but I have not found a book on C++ that satisfactorily answers these type of questions.

C++ project organisation (with gtest, cmake and doxygen)

I would like to use a global set of flags for compiling a project, meaning that at my top-level CMakeLists.txt file I have specified:

    ADD_DEFINITIONS ( -Wall -Weffc++ -pedantic -std=c++0x )

However, for a specific file (let&#39;s say &quot;foo.cpp&quot;) in a subdirectory, I want to switch the
compile flags to not apply -Weffc++ (included commercial library I cannot change).  To simplify the situation to use only -Wall, I tried:

     SET_SOURCE_FILES_PROPERTIES( foo.cpp PROPERTIES COMPILE_FLAGS -Wall )
     ADD_EXECUTABLE( foo foo.cpp )
, which did not work.
I also tried

    SET_PROPERTY( SOURCE foo.cpp PROPERTY COMPILE_FLAGS -Wall )
    ADD_EXECUTABLE( foo foo.cpp )
and

    ADD_EXECUTABLE( foo foo.cpp )
    SET_TARGET_PROPERTIES( foo PROPERTIES COMPILE_FLAGS -Wall )
, in which neither worked.

Finally, I tried removing this defintion:

    REMOVE_DEFINITIONS( -Weffc++ )
    ADD_EXECUTABLE( foo foo.cpp )
    ADD_DEFINITIONS( -Weffc++ )
, which also did not work (meaning, I get a lot of style warnings about the commercial library).
(**Note: The warnings ARE suppressed if I DO NOT re-include the -Weffc++ directive after the executable is built.)

I also tried temporarily removing the compile flags:
http://www.cmake.org/pipermail/cmake/2007-June/014614.html
, but that didn&#39;t help.

Is there not an elegant solution to this?

Content Type	Original Author	Original Content on Stackoverflow
Question	Sasha	View Question on Stackoverflow
Solution 1 - Cmake	Fraser	View Answer on Stackoverflow

How do I initialize a CMake variable with the result of a shell command

Cmake Problem Overview

Cmake Solutions

Solution 1 - Cmake

how to fix the issue "Command /bin/sh failed with exit code 1" in iphone

actionbar up navigation with fragments

Attributions