Dear Eric,
Thank you for your explanation. I think the mistake I made was that ctest is
used to compare the generated result with the expect result, such that the
return value 1 means that the program runs fine. However, what I was trying to
do is just to automatically run the executable with p
On 08.01.2010, at 02:25, Alexander Neundorf wrote:
On Thursday 07 January 2010, Claus Klein wrote:
Hi
i want to install a cross compiled (build host is a MAC OS X) project
to a temporary state dir to get an archive to distribute the
binaries.
The target is win32 (mingw), compiled to be ins
For whatever command I am using if I insert a wild card to be passed in e.g.
INSTALL_COMMAND cp blah/* ${MY_STAGING}
becomes cp "blah/*"
which will then yield an error.
Is there some escape sequence I'm missing to avoid the quoting?
--
Cheers,
Timothy St. Clair
___
- "James Bigler" wrote:
> On Wed, Jan 6, 2010 at 11:00 PM, Luke Parkinson < lparkin...@vpac.org >
> wrote:
>
>
Hello Everyone,
>
> I apologise in advance if this is the wrong way to revive an old topic, but I
> wasn't sure how to reply to old threads in the mailing list and I'm new t
Not a problem - figured putting together some clean templates could
probably help me and my colleagues out too, anyway.
Your comment about the syntax makes me understand a bit better...
"MyPackage" isn't a name, it's a placeholder for one of the many general
packages of third party functionality
On Thu, Jan 7, 2010 at 4:00 PM, Jed Brown wrote:
> On Thu, 07 Jan 2010 15:54:33 -0600, Ryan Pavlik
> wrote:
> > If you use the _LIBRARIES variable, you don't need to even mess around
> > with the imported targets thing
>
> Dumping recursive dependencies in *_LIBRARIES causes overlinking, they
>
On Wednesday 06 January 2010, Claus Klein wrote:
> Yes, I did it again and again with rm -rf build.
> Same result!
>
> As I said: "The problem occurs always when I run cmake again, no
> matter of Windows or Windows-gcc is used."
I don't see a way how cmake itself should come up with "Windows-gcc"
>
>
> What kind of errors were you getting?
>
>
I would point to a URL on GMane for the thread titled "Build only what you
need in third party libs" , but it looks as though Gmane does not have all
the postings. I was getting bounces back from CMake mailing list due to
size of email.
Here is an e
Wow, thanks for the elaborate answer!
I learn a lot just going through the examples.
One thing for me to understand first:
> Ah, so if those components are always necessary (that is, A always needs B,
> and B always needs C), there's no need to use the "components" option.
Ah, I found the compone
On Thu, 07 Jan 2010 15:54:33 -0600, Ryan Pavlik wrote:
> If you use the _LIBRARIES variable, you don't need to even mess around
> with the imported targets thing
Dumping recursive dependencies in *_LIBRARIES causes overlinking, they
should only be there when linking statically.
Jed
_
Ah, so if those components are always necessary (that is, A always needs
B, and B always needs C), there's no need to use the "components"
option. Just zip through them in this way - _LIBRARY (cache var) is a
single library, _LIBRARIES (not a cache var) is the list containing the
library and al
Hi Paul,
yes, I do it in this way and it works good.
Only if the target system is Windows, there may be a Problem if prefix
is something like "C:/programs" ...
But in most embedded unix like systems, there is no problem.
Claus
On 07.01.2010, at 21:30, Paul Chavent wrote:
Hi cmake mai
Hi cmake mailing list !
When i cross compile with autotools, i used to do
$ ./configure --prefix=/usr/local ...
$ make install DESTDIR=${SYSROOT}
Now, with cmake i do
$ cmake source_dir -DCMAKE_INSTALL_PREFIX=/usr/local ...
$ make install DESTDIR=${SYSROOT}
Is it a good practice ?
What is t
Hi Ryan,
thanks very much for your answer.
For clarification, the package I would like to link against has (say)
three components A, B, C, where A at link time needs symbols of B
needs symbols of C needs symbols of some external libs.
I would like to make sure that the user can say
FIND_PACK
On Wed, Jan 6, 2010 at 10:41 PM, Brian Davis wrote:
>
>
> On Tue, Jan 5, 2010 at 12:23 PM, James Bigler wrote:
>
>>
>>
>>> I ask my self two questions:
>>>
>>> 1) Why is CUDA_NVCC_FLAGS not set to some default build setting that
>>> would just work out of the box? - I get the answer to this quest
On Wed, Jan 6, 2010 at 11:00 PM, Luke Parkinson wrote:
> Hello Everyone,
>
> I apologise in advance if this is the wrong way to revive an old topic, but
> I wasn't sure how to reply to old threads in the mailing list and I'm new to
> this list. I'm part of a team of developers looking at integra
Hello,
My apologies in advance if I'm completely mis-reading your question and
if this answer seems way off base: just addressing what seemed like the
most likely issue from the info you provided. (This link below [1]
might help you get better results out of mailing lists.)
A script called
Ryan Pavlik wrote:
Hello -
This might help - from http://www.vtk.org/Wiki/CMake_Scripting_Of_CTest
# set any extra environment variables to use during the execution of the script
here:
SET (CTEST_ENVIRONMENT
)
\
You need quotes around the set:
Something like this works:
SET(TESTARG /path/
Hello -
This might help - from http://www.vtk.org/Wiki/CMake_Scripting_Of_CTest
# set any extra environment variables to use during the execution of
the script here:
SET (CTEST_ENVIRONMENT
)
My guess is it creates an empty/default environment when running tests
(rather than inheriting), and you
Maybe we never explicitly stated this, but the system is in fact a 64-bit
Windows OS, so %PROCESSOR_ARCHITECTURE% is correctly AMD64 for our system when
viewed from a 64-bit process such as cmd.exe and our batch script. The project
that we are building only supports 32-bit compilation in Window
Classification: UNCLASSIFIED
Caveats: NONE
Fellow Cmake Users-
I am trying to set environment variables (namely PATH and PYTHONPATH) on
Windows during test execution. I utilize a configuration script which gets
converted from a .cmake.in to .cmake, then is used to call each of my tests.
The top
Hi Michael,
I added to the FindMypackage.cmake in the FOREACH(COMPONENT) loop the
following snipped
ADD_LIBRARY(${COMPONENT} STATIC IMPORTED)
SET_TARGET_PROPERTIES( ${COMPONENT} PROPERTIES
IMPORTED_LOCATION "${${UPPERCOMPONENT}_LIBRARY}"
Paul Smedley wrote:
Windows does 8.3 mapping? Can you point to this in the cmake source?
I wasn't aware of any windows restrictions of DLL filenames.
Yes, there is a windows function to get a shore path name:
GetShortPathName(tempPath, buffer, size);
Setting up a dashboard should not be t
Hi all,
Last month, I gave a tech talk at the google NYC office. It is now up
on youtube. Here is the link:
http://www.youtube.com/watch?v=8Ut9o4OdSC0&feature=youtube_gdata
Enjoy!
-Bill
--
Bill Hoffman
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065
bill.hoff...@kitware.com
http:
Never Mind, I found the errant include directive.
I do apologize.
> -Original Message-
> From: cmake-boun...@cmake.org
> [mailto:cmake-boun...@cmake.org] On Behalf Of Smith Jack
> (Ext. - UGIS - UniCredit Group)
> Sent: Thursday, January 07, 2010 9:34 AM
> To: cmake@cmake.org
> Subject:
+Edited for brevity.
> In the Help menu go to "About Eclipse" then click on "CDT"
> icon this will show you your CDT version.
Eclipse C/C++ Development Tools - Mylyn Bridge
Version: 5.1.0.200909110608
Build id: 200909110608
> Is eclipse OK when you create a CDT project usin
2010/1/7 Smith Jack (Ext. - UGIS - UniCredit Group)
:
>
> CMake: cmake version 2.6-patch 2
This is a relatively old CMake version (Sept. 2008)
could you by any chance try a more recent one?
May be CMake 2.8.0 or even 2.6.4?
http://www.cmake.org/cmake/resources/software.html
> Eclipse Platform:
Dear CMake developers,
I am building cmake 2.8.0 on Linux (CentOS 5.4) using the options:
./bootstrap --prefix=/cluster/apps/cmake/2.8.0 --datadir=share
--docdir=doc --mandir=man
Everything goes fine, except that when I execute "make install" the name of
some installation directories i
Hi Nico
In that case you need to do this:
add_library(${COMPONENT} IMPORTED)
set_target_properties(${COMPONENT} PROPERTIES
IMPORTED_LOCATION "${${COMPONENT}_LIBRARY}"
LINK_INTERFACE_LIBRARIES "${${COMPONENT}_LINK_INTERFACE_LIBRARIES}"
)
where each of the components X has a variable X_LIBRA
Hi Michael,
thanks for the explanations.
I'm indeed about to write a FindModule.cmake for a library which I did
*not* write, but to certain components of which I'd like to link
against using CMake (in a clean fashion).
I'm FOREACHing through the components of the library, and upon trying to set
On 7. Jan, 2010, at 10:51 , Nico Schlömer wrote:
> Hi,
>
> I'm writing a FintMymodule.cmake file for a set of libraries (read:
> components), and with the given examples in the official CMake/Modules
> folder it comes along nicely.
>
> One thing I couldn't figure out now is how to set link depe
Hi,
I'm writing a FintMymodule.cmake file for a set of libraries (read:
components), and with the given examples in the official CMake/Modules
folder it comes along nicely.
One thing I couldn't figure out now is how to set link dependencies
between the different components; that is, if I link aga
> -Original Message-
> From: cmake-boun...@cmake.org
> [mailto:cmake-boun...@cmake.org] On Behalf Of Alexander Neundorf
> Sent: Tuesday, January 05, 2010 7:52 PM
> To: cmake@cmake.org
> Subject: Re: [CMake] Does Cmake add 'standard' include paths ?
>
> On Tuesday 05 January 2010, Smith Jac
>> I wrote the batch script that Joe is using - the AMD64 in the build
>> directory path is just a consequence of using %PROCESSOR_ARCHITECTURE% to
>> create the build directory from the batch script and is purely a cosmetic
>> issue.
I'm failing to make sense (my fault only) of what's goin
34 matches
Mail list logo
