As demonstrated here https://github.com/QIICR/dcmqi/pull/79, the
problem is resolved when .cmd versions of the commands are used.
On Wed, Aug 24, 2016 at 1:10 PM, Andrey Fedorov
wrote:
> Hi,
>
> we are running ctest's on appveyor using npm-installed packages.
> Specifically, we
Hi,
we are running ctest's on appveyor using npm-installed packages.
Specifically, we run jsonlint and ajv on json files to validate the
content.
Packages are installed in this line:
https://github.com/QIICR/dcmqi/blob/master/appveyor.yml#L12-L13 of the
appveyor configuration.
The installed pack
Hi,
One of my tests generates a report table (file in text format). I
would like to see its content after each ctest (or make test)
invocation. Is there any way to achieve that?
I noticed that tests targets have ATTACHED_FILES property, though it
looks like it has no effect on ctest run when dashb
lar, before
`copy_generating_resource` is run.
Am I missing something?
Andrey Mishchenko
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
info
ilding the clsparse project (the dependencies change very seldom).
> However, visual studio's intellisense does start indexing boost and gmock
> because they are included in clsparse like any other header file or library,
> so they become 'browseable' through the IDE.
generated
> for the library thereafter. I've not tested QT Creater, but I'll see if I
> can verify your difficulties next week.
> ____
> From: Andrey Pokrovskiy [wonder.m...@gmail.com]
> Sent: Thursday, August 20, 2015 2:29 PM
> To: K
Such approach doesn't work with IDE. For example, when I open main
CMakeLists.txt in Qt Creator I only see two *.cmake files. Superbuilds
use ExternalProject_Add() which kills a lot CMake benefits when used
for CMake project from CMake project.
On Thu, Aug 20, 2015 at 9:28 AM, Knox, Kent wrote:
>
Hi,
What is best way to organize a library project that uses CMake as its
build system?
One advantage that I would expect from a library project with CMake
build system is easy integration with another projects that also use
CMake. In other words it should be very simple to include (add a
dependen
I don't like my current solution for such problem, but it works for me
well. Note "file(GLOB_RECURSE ..." and custom "copy" step in the end.
Also you can try to google "cmake super build" which probably will
provide you more ideas.
include(ExternalProject)
set(WEBSOCKETS_PATCH_DIR "${CMAKE_CU
y wrote:
> Andrey Pokrovskiy wrote:
>
>> /* I'm using cmake-3.2.20150331-gb190c. */
>>
>> I have a following construction:
>>
>> ExternalProject_Add(
>> websockets_ep
>> DEPENDS ev openssl
>> ...)
>>
>> But i
/* I'm using cmake-3.2.20150331-gb190c. */
I have a following construction:
ExternalProject_Add(
websockets_ep
DEPENDS ev openssl
...)
But it so happened, that "openssl" is a INTERFACE library. Because of
that I get an obscure error:
CMake Error at
/usr/share/cmake/shar
this "super-build" thing in case
my solution will not scale too well.
[1] http://www.cmake.org/pipermail/cmake/2015-February/059885.html
On Tue, Feb 17, 2015 at 9:58 PM, Jean-Christophe Fillion-Robin
wrote:
> Hi Andrey,
>
> On Tue, Feb 17, 2015 at 5:52 PM, Andrey Pokrovskiy
&
Hi,
Current CMake disallows Interface Libraries to have dependencies.
However, I suspect that was done for a reason. Here is the commit for
that change:
commit 6db7e6d24c68085f16dcf6d8a86ae0f74e9a1f01
Author: Stephen Kelly
Date: Wed Dec 25 15:11:50 2013 +0100
add_dependencies: Disal
CMake already has a concept of "libraries" (added with add_library).
There should be a way of saying "Hey, this static library comes from
that external project. It also requires such and such include
directories".
On Tue, Feb 17, 2015 at 1:53 PM, Jean-Christophe Fillion-Robin
Hi,
I'm using ExternalProject_Add() to build OpenSLL library. After
install step I have following artifacts available:
* libcrypto.a
* libssl.a
* include/openssl/*.h
I wonder, what is the "canonical" way to make those artifacts
available for other targets in the project?
FindPackage style thing
Hi,
I noticed that when I explicitly specify OUTPUT_DIR for add_jar, like this:
add_jar(demo
SOURCES Main.java
OUTPUT_DIR ${EXECUTABLE_OUTPUT_PATH})
All intermediate files for that target also go to specified output dir.
So I end up with ./CMakeFiles/demo.dir directory in my
${EX
Let's say:
set(WORDS "cat" "dog")
and then:
""
which will produce "cat\ dog" instead of "cat dog".
Looks like a bug to me.
Minimal example to reproduce the issue.
File - CMakeLists.txt:
cmake_minimum_required(VERSION 3.1)
project(escape_me_not)
set(WORDS "cat" "dog")
add_custom_command(OUTPUT
On Mon, Nov 17, 2014 at 10:26 PM, Stephen Kelly wrote:
> avo...@mail.ru wrote:
>
>> What should I add
>> to B/CMakeLists.txt to successfully build my executable?
>
> You might be able to add an INTERFACE library and populate its
> INTERFACE_SOURCES using the target_sources command:
>
> http://www
it's
here https://gist.github.com/oliora/4961727299ed67337aba
Andrey
On Fri, Nov 7, 2014 at 4:56 PM, Andrey Upadyshev wrote:
> Thank you for advice Petr! I will go with this solution if can't find
> another one. CMake macroses are slightly weird so I'm trying to avoid the
Thank you for advice Petr! I will go with this solution if can't find
another one. CMake macroses are slightly weird so I'm trying to avoid them
:)
On Fri, Nov 7, 2014 at 4:39 PM, Petr Kmoch wrote:
> Hi Andrey.
>
> As a workaround, you could make the calling context a
kage to set all variables
in my function caller's scope? I.e. something like find_package(...
PARENT_SCOPE)?
Thank you,
Andrey
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support
Hi Stefan,
You should add CMake command option
*-T vc120_xp*
BR,
Andrey Upadyshev
On Sun, Dec 8, 2013 at 7:22 PM, Stefan Fendt wrote:
> Hi,
>
> I'm using CMake 2.8.12 together with MSVC 2013 and need to produce a
> binary which is (still) compatible with Windows XP SP3.
>
В Sat, 2 Apr 2011 14:08:36 -0400
David Cole пишет:
> Try with CMake 2.8.4 -- we fixed some parallel make propagation issues
> in 2.8.3 or 2.8.4... Using "$(MAKE)" now. Should avoid the problem
> you're reporting here.
Your advice for 2.8.2 solved the problem, thanks David.
BUILD_COMMAND = $(MAKE
Hi.
I have problem with make -jN and Cmake ExternalProject.
% alias make="make -j5"
% make
Scanning dependencies of target EXTLIB
[ 0%] Creating directories for 'EXTLIB'
[ 0%] No download step for 'EXTLIB'
[ 0%] [ 0%] No patch step for 'EXTLIB'
No update step for 'EXTLIB'
[ 0%] No configure s
08.06.10, 00:44, "Alexander Neundorf" :
> Can you please put all that in the cmake bug tracker
> (http://public.kitware.com/Bug) so all that information doesn't get lost ?
I've posted a bug #10823.
You can find it at [1].
[1] http://public.kitware.com/Bug/view.php?
the location of the target Qt
> installation, i.e. the lib and include dirs ?
In general, no.
Any such relation is either quite cross-environment specific or non-existent.
For example,
1) moc and uic are located at /home/me/cross-devel/tools/bin
2) target lib dir is /home/me/cross-devel/build/my_in
bunch of set() statements
> > and a couple of include() directives.
>
> Yes, what makes FindQt4.cmake big is all the flexibility to find everything
> for the different versions on the different OSs. It started small...
In addition, there are a great number of Qt components, which magnifie
ngs that prevent
> cross-compiling the last few cmake releases. It could probably go a bit
> quicker, but I wanted to be careful to not break things.
Yeah, I greatly appreciate these efforts!
Many packages compile flawlessly for both native and cross
ccessfully compile a qt4-based
application with such a hacked FindQt4.cmake with bunch of set() statements and
a couple of include() directives.
> CC'ing the cmake -list.
OK.
--
Andrey Hippo.
___
Powered by www.kitware.com
Visit other Kitwar
ag2__ ). In this case no keys were defined... It's very
strange, because CMake's documentation present usage example with multiple
properties in one command. I solved this issue with variable which contains
all needed keys.
--
-- Andrey
___
>From documentation to CMake 2.6.x:
"Note that the PRE_BUILD option is only supported on Visual Studio 7 or
later. For all other generators PRE_BUILD will be treated as PRE_LINK."
What are you actually trying to do?
If you want to perform some actions before actually build the target, use of
add
riate configuration?
>
> I also was not able to find CMAKE_BUILD_STATUS in the 2.6 documentation.
> Where can I read about this variable?
>
> On Sun, Dec 21, 2008 at 1:49 PM, Andrey Sploshnov <
> ice.nightcraw...@gmail.com> wrote:
>
>> May be you need somethin
May be you need something like this?
include_directories (C:\includes\foo\all)
if (CMAKE_BUILD_STATUS STREQUAL "Debug")
include_directories (C:\includes\foo\debug)
elseif (CMAKE_BUILD_STATUS STREQUAL "Release")
include_directories (C:\includes\foo\release)
endif (CMAKE_BUILD_STATUS STREQU
On Mon, Feb 26, 2007 at 07:22:19PM +0100, Thomas Klausner wrote:
> I'm trying to make the cmake-2.4.6 package in pkgsrc depend on the
> xmlrpc-c-1.09.00 package. I already managed to make cmake depend
> on pre-installed curl, expat, and zlib libraries.
>
> The problem I see with xmlrpc-c is that
On Mon, Oct 16, 2006 at 11:24:58AM -0700, Alan W. Irwin wrote:
> The obvious solution is to build it internally. When KDE used this
> library was that the option chosen?
True for SIM.
> If so, could you point me to the CMake files used to build libltdl?
We switched from libltdl prior to using cm
On Sat, Sep 30, 2006 at 08:34:58AM -0700, Alan W. Irwin wrote:
> However, libltdl does not solve the issue of how to dynamically load
> plug-ins on windows systems.
SIM always used libltdl on all platforms without problems (until we
switched to QLibrary).
--
WBR, wRAR (ALT Linux Team)
signature
On Sat, Sep 30, 2006 at 11:47:33AM -0700, Alan W. Irwin wrote:
> Excuse my windows ignorance, but is LoadLibrary the standard way to
> dynamically load plug-ins for all the varieties of windows?
Yes.
--
WBR, wRAR (ALT Linux Team)
signature.asc
Description: Digital signature
On Wed, Sep 27, 2006 at 10:42:30AM +0200, Axel Roebel wrote:
> IF("${CMAKE_SYSTEM_PROCESSOR}" STREQUAL "x86_64")
That is not correct. Every shared lib should be compiled with fPIC, on
x86_64 or not. Yes, shared libs with TEXTREL can work on x86, but it
doesn't mean that it's OK to compile them with
On Tue, Sep 26, 2006 at 07:33:44PM -0700, Alan W. Irwin wrote:
> Could you clarify your goal here?
Linking of shared lib (being built) with objects from static lib (built
with cmake). Here the objects from the static lib are compiled without
-fPIC.
--
WBR, wRAR (ALT Linux Team)
signature.asc
De
39 matches
Mail list logo
