nja
(maybe there are others too?) but I don't know how. I was previously doing
something like
```
if (ENV{VERBOSE})
message("g++ ${SOURCE}")
endif ()
execute_process(COMMAND g++ ${SOURCE})
```
but Ninja doesn't set an environment variable. Is it possible do this?
Hello all,
This problem does not exist in Linux - I have perfect compilation there.
Windows, however, is throwing the following error:
CMake Error: cmListFileCache: error can not open file
C:/Users/David/Documents/GitHub/PropWare
CMake Error: Could not find cmake module file:
The "ca
Hello all,
I have a working (in Linux) CMake project and am now trying to make it
cross-platform. I'm nearly there! CMake generates the Makefiles without
error but upon trying to run Make, things die. Here's the output from
"make VERBOSE=1"
C:\Users\David\Documents\GitHub\PropWare>make VERBO
t; Sent: Sonntag, 17. August 2014 01:51
> To: David Zemon
> Cc: cmake@cmake.org
> Subject: Re: [CMake] No Such File or Directory
>
> On 2014-08-16 15:02-0500 David Zemon wrote:
>
> > Hello,
> >
> > After downloading the 3.0.1 binary Linux distribution o
Hello,
After downloading the 3.0.1 binary Linux distribution of CMake, I am
running into the following bash error:
*david@fresh-ubuntu:~/**PropWare/util$* cmake
bash: /home/david/cmake-3.0.1-Linux-i386/bin/cmake: No such file or
directory
*david@fresh-ubuntu:~/**PropWare/util$* whi
LE_OPTIONS "-Os")
set_property(DIRECTORY "/root/p2" PROPERTY COMPILE_OPTIONS "-O1")
or you just use the add_compile_options command in all 3 CMakeLists.txt files.
The CMakeLists.txt files in root/p1 and root/p2 will inherit the compile
options set in the parent root/CMa
the add_compile_options command in all 3 CMakeLists.txt files.
The CMakeLists.txt files in root/p1 and root/p2 will inherit the compile
options set in the parent root/CMakeLists.txt file.
--
Glenn
On 3 August 2014 23:46, David Zemon <mailto:da...@zemon.name>> wrote:
Hello,
Hello,
For the simple case of three directories and two projects - /root,
/root/p1, and /root/p2 - I would like to set some common flags for both
projects and then other flags should be independent. For instance, p1
should be compiled with "-std=c99 -Os" and p2 should be compiled with
"-std=c
I am attempting to build an easy-to-use build system for an embedded
system. This chip uses .dat, .spin, .cogc, and .ecogc files along with
.S, .c, and .cpp. I've added the necessary language files to my project
path which will enable cogc (I'll get to the other file types
eventually) and they
