I need the files to be copied at build time, not a compile time: They are
files I am editing and I need the build system to export the files to the
binary directory tree whenever they are changed.
I know it looks stupid and probably is as well :-) The reason is that when
the project is being used
On Wed, Jun 27, 2012 at 2:59 AM, Rolf Eike Beer wrote:
>> Sigh, now I sent you the code from the wrong directory, but the code for
>> the "Backend" component is virtually identical. I don't know how to use
>> functions with CMake, so I simply made a verbatim copy of the below code
>> in
>> each s
> Sigh, now I sent you the code from the wrong directory, but the code for
> the "Backend" component is virtually identical. I don't know how to use
> functions with CMake, so I simply made a verbatim copy of the below code
> in
> each subfolder and edited it to match the subfolder. So the Backen
Problem solved. I only needed to update to the most recent version. So I
figure I initially used a CMake that worked, then updated (which broke it),
and then updated (which repaired it).
Sorry for having wasted bandwidth and your time - when one uses bleeding
edge technologies, one has to rememb
FYI: On Linux (using CMake v2.8.8 and a recent Ninja), the Ninja build
works as expected. Just like it used to do on Windows. I now suspect the
problem is related to the CMake version I use (cmake version
2.8.8.20120605). I picked it up somewhere I don't recall and that's
probably the cause of t
Sigh, now I sent you the code from the wrong directory, but the code for
the "Backend" component is virtually identical. I don't know how to use
functions with CMake, so I simply made a verbatim copy of the below code in
each subfolder and edited it to match the subfolder. So the Backend
project
Here goes:
project(Driver)
set(PublicHeaders
"Driver.hpp"
"Setup.hpp"
)
set(PublishedHeaders "")
foreach(Header IN LISTS PublicHeaders)
get_filename_component(HeaderFilename "${Header}" NAME)
set(Source "${CMAKE_CURRENT_SOURCE_DIR}/${Header}")
set(Output "${CMAKE_CURRENT_BINAR
On Tue, Jun 26, 2012 at 6:40 PM, Mikael Lyngvig wrote:
> Ohh, sorry. Ninja says:
>
> [117/325] Building CXX object Driver/CMakeFiles/Driver.dir/Driver.cpp.obj
> FAILED: c:\Mingw64\bin\c++.exe -DNDEBUG
> -DBR0_BUILD_ASSERT=BR0_BUILD_ASSERT_DELETE
> -DBR0_BUILD_CHARSET=BR0_BUILD_CHARSET_ASCII
> -
Ohh, sorry. Ninja says:
[117/325] Building CXX object Driver/CMakeFiles/Driver.dir/Driver.cpp.obj
FAILED: c:\Mingw64\bin\c++.exe -DNDEBUG
-DBR0_BUILD_ASSERT=BR0_BUILD_ASSERT_DELETE
-DBR0_BUILD_CHARSET=BR0_BUILD_CHARSET_ASCII
-DBR0_BUILD_ENDIAN=BR0_BUILD_ENDIAN_LITTLE
-DBR0_BUILD_MODE=BR0_BUILD_
On Tue, Jun 26, 2012 at 6:30 PM, Mikael Lyngvig wrote:
> No, I delete the entire build tree (I build out of the source tree, btw).
>
> The procedure is as follows:
>
> rem foo contains the source code
> md foo-build
> cd foo-build
> cmake -G Ninja ..\foo
> ninja
> rem fails as de
No, I delete the entire build tree (I build out of the source tree, btw).
The procedure is as follows:
rem foo contains the source code
md foo-build
cd foo-build
cmake -G Ninja ..\foo
ninja
rem fails as described earlier
cd ..
rd /s /q foo-build
md foo-build
cd
You can't switch generators in the same build tree without deleting
absolutely everything and starting over.
Is that what you're trying to do?
If you want a make build tree and a ninja build tree, you'll need two
separate build trees
HTH,
David
On Tue, Jun 26, 2012 at 4:45 PM, Mikael Lyng
Hi,
I am a fan of Ninja. Since I started using it, everything's been built
much, much faster than before. Among other things because I use CMake to
publish headers to the binary directory so as to allow me to include the
headers with a relative path without having to move all my headers to a
cen
13 matches
Mail list logo
