I have¹ a CTest like:
execute_process(...)
set(expected "
...text...
...text...
")
string(REGEX MATCH ${expected} match ${out})
So, basically, I'm checking that the process outputs a certain set of
lines, and taking advantage of multi-line strings in CTest script for
convenience and readabilit
Thanks Angeliki. I will try to do something like this. In fact I forgot to
mention that my target which collide comes from add_custom target() but I can
apply the same principle.
To be more precise about the context, my projects have a target "unit_test"
which is run tests each time I build (i
Hi Aurelien,
Even though it is unsafe and not recommended, you could set policy CMP0002
to old so that cmake silently accepts non-unique target names like this:
cmake_policy(SET CMP0002 OLD)
I can't guarantee that your build will then work however.
Another option is to write your own wrapper to
Is there a reason, why you treat your independent projects with add_directory()
instead of making them external projects?
--
Gruesse,
Jakub
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Aurelien Richez
Sent: Donnerstag, 27. März 2014 14:58
To: cmake@cmake.org
Subject: [CMake] target
Hi,
I have two project that are independent and can be compiled on their own. I
also have a bigger project which include these two project with
add_subdirectory. However, these projects contain targets with the same names.
As a consequence, cmake 2.8 complains with a message such as "another t
Solved the problem.
Further verification revealed that, when I build "PACKAGE", it generates a
"install_manifest.txt" file in my build directory. It contains absolute
paths to copy of install files I mentioned using "install targets" command.
This temporary directory and its files are also created
>
> I am no NSIS expert so I can't imagine why 'File /r "${INST_DIR}\*.*"'
> could possibly do ???
>
About the file command the NSIS documentation says this:
Adds file(s) to be extracted to the current output path ($OUTDIR).
If the /r switch is used, files and directories are added recurs
2014-03-27 7:08 GMT+01:00 Lloyd :
> Hi,
>
> My CMake file contains the install comands like this
>
> install(TARGETS MyExe RUNTIME DESTINATION .)
>
> When I use the standard NSIS template, the installer is created with
> "MyExe". But our project needs a custom NSIS template so I have written one,
>
