Cmake:Set Environment Variables from a Script

cmake : Set environment variables from a script

Reading through the cmake quick start, you can specify variable on a command line:

cmake -DVARIABLE1=value1 -DVARIABLE2=value2 ...

Otherwise, set command in the cmake script is probably what you want, see the reference manual. To set the environment variable PATH, do:

set(ENV{PATH} "/home/martink")

To set normal variable, do:

set(variable "value")

Not sure which ones you have to set, probably the environment ones.

That said, setting environment variable prior to calling cmake is often the easiest solution to solve the problem. If you want a cross-platform way to do this that doesn't depend on the syntax of a specific shell to set environment variables, there is the cmake -E env command.

How to source environment variables from a script on a remote host when using remote mode in clion?

Unfortunately, as of 13.11.2020 there is no way to source a script from the remote machine while working in CLion remotely via ssh.

There is a ticket for this functionality to be added so if you are reading this in the future, check the web, maybe the situation has changed.

How to modify environment variables passed to custom CMake target?

A portable way of setting environment variables for a custom target is to use CMake's command-line tool mode command env:

env [--unset=NAME]... [NAME=VALUE]... COMMAND [ARG]...

Run command in a modified environment.

E.g.:

add_custom_target(newtarget ${CMAKE_COMMAND} -E env NAME=VALUE somecommand)

Also see Command Line Tool Mode.

How to set environment variables in CMake so that they can be visible at build time?

Maybe what you want is CMAKE_XCODE_ATTRIBUTE_<an-attribute>

https://cmake.org/cmake/help/latest/variable/CMAKE_XCODE_ATTRIBUTE_an-attribute.html

How to reference CMake variable in shell script

CMake variables are not environment variables.

You can set an environment variable like so:

set(CMAKE_C_FLAGS ...)
set(ENV{CMAKE_C_FLAGS} "${CMAKE_C_FLAGS}")
execute_process(COMMAND "${CMAKE_CURRENT_SOURCE_DIR}/my_script.sh")

Note that this lasts only for the duration of the CMake configure step. This means it will work with execute_process, but not add_custom_command.

Also note that calling a shell script from CMake is a code smell (hinders portability, is weird and probably unnecessary).

---

Related Topics