On 01/20/2017 12:59 AM, Aaron Boxer wrote:
I have a test in my ctest suite that fails both with
and without a ! at the beginning of the test.
So,
FOO -BAR -BAZ
fails
and
!FOO -BAR -BAZ
fails.
I am not aware of "!" having any special meaning in the context of
CTest. Can you elaborate?
I have a test in my ctest suite that fails both with
and without a ! at the beginning of the test.
So,
FOO -BAR -BAZ
fails
and
!FOO -BAR -BAZ
fails.
Any ideas, or how can I get more info on the failure ?
Thanks.
Aaron
--
Powered by www.kitware.com
Please keep messages on-topic and check
If you are using symbol visibility/exports, then marking the symbol as
exported may prevent the linker from removing it if the code is going into
a shared library (including static libraries that are built up into a
shared library). It's not a trivial topic though, so you would need to do
some read
Thanks Mike
The motivation for linking explicitly with the object file was in the PS at the
bottom, although only very brief of course.
The registry.cxx file has static variables with constructors with side effects
(they add entries to a std:::map that registers "factories"). Therefore,
regis
Ah, sorry, I misunderstood what CCACHE_DIR was for. Nevertheless, the
method in that linked article could be easily modified to do what you want.
Simply add the setting of the environment variable to the launch scripts.
Since those launch scripts are copied across to the build dir at configure
time
On Thu, Jan 19, 2017 at 4:44 PM, David Lind wrote:
> That’s not the issue. The issue is telling ccache where to place it’s
> cache files. If I compiles for toolchain X, Y and X, I need to set
> CCACHE_DIR accordingly. Otherwise the cache will be useless.
>
>
https://ccache.samba.org/manual.html#_
Scott,
I have find_program implemented to find ccache, as shown below.
find_program(CCACHE ccache)
if(CCACHE)
set_property(GLOBAL PROPERTY RULE_LAUNCH_COMPILE ${CCACHE})
set_property(GLOBAL PROPERTY RULE_LAUNCH_LINK ${CCACHE})
endif()
That’s not the issue. The issue i
Rather than relying on environment variables, you can use CMake's
find_program() command to find ccache on your path and then tell CMake to
use that as a launcher. You can find an article with a detailed explanation
of how to set this up here:
https://crascit.com/2016/04/09/using-ccache-with-cmake
I am porting existing makefiles to cmake. One of the key features of these
makefiles is setting the CCACHE_DIR environment variable based upon the tool
chain selected.
I have TC_.cmake files created. Ideally, I would add a line to these
files to set the CCACHE_DIR. But, CMake doesn’t have the a
Aldi,
> I believe spack is the closest to what I need. However, all these
> solutions (hunter, conan, spack...) have perhaps their strongest focus
> in packaging, dependencies, automatic downloads, etc... while I prefer
> to do all such tasks myself. I prefer to not have packages, just
download
I think my initial reaction to installing a source (cxx) file is that you
should install a static library instead (.a) - which is basically what you are
suggesting. Just define a new static library target that includes the cxx file
and install it…should work fine. If there are headers needed to
Am 19. Januar 2017 15:26:47 MEZ schrieb "Gonzalo Garramuño"
:
>
>
>El 19/01/17 a las 05:30, Wagner Martin escribió:
>>
>> However, CMake needs to include version.cmake at first CMake run
>time,
>> which is not possible because it’s a generated file.
>>
>> Is there any other way to do the rename
Typo in my last message: All occurrences of CMAKE_INSTALL_PREFIX were
meant to be CMAKE_PREFIX_PATH instead.
On Thu, Jan 19, 2017 at 2:57 PM, ardi wrote:
> Thanks a lot, Elisabeth, Domen, Guillaume, and Konstantin,
>
> I believe spack is the closest to what I need. However, all these
> solutions
Hi,
We use for our complex project the Cmake 2.4 for vXworks compiler from
windriver.
For the new project we want to update the cmake to 3.7.2, but vxworks is not
yet supported any more.
Therefore we have written an alternative toolchain file which is started with
the following commando:
cma
El 19/01/17 a las 05:30, Wagner Martin escribió:
However, CMake needs to include version.cmake at first CMake run time,
which is not possible because it’s a generated file.
Is there any other way to do the rename?
You will need to do the install as another target/command. For example:
Thanks a lot, Elisabeth, Domen, Guillaume, and Konstantin,
I believe spack is the closest to what I need. However, all these
solutions (hunter, conan, spack...) have perhaps their strongest focus
in packaging, dependencies, automatic downloads, etc... while I prefer
to do all such tasks myself. I
That doesn't work as CMake seems to only evaluate the include() statement once
at first run. With the OPTIONAL statement, my project builds, but the
${version_string} variable is not populated.
Von: Eric Noulard [mailto:eric.noul...@gmail.com]
Gesendet: Donnerstag, 19. Januar 2017 13:00
An: W
You can try:
include(version.cmake OPTIONAL)
which will make include tolerate the absence of version.cmake,
but then your install statement will only be OK after version.cmake has
been created.
2017-01-19 9:30 GMT+01:00 Wagner Martin :
> Hello,
>
>
>
> I’ve searched for some time, but didn
Hello,
I’ve searched for some time, but didn’t find anything useful. Most finds deal
with including version system stuff passed to header files for compilation.
I want to achieve something like that:
Include(version.cmake)
install(FILES firmware.hex RENAME firmware_${version_string}.hex)
wher
19 matches
Mail list logo