On Wed, Jun 10, 2009 at 9:13 PM, Dong Tiger idlecat...@gmail.com wrote:
Hi,
It will be very convenient to be able to specify some environment variables
when a unit test runs. Currently, the only way I know is using shell script
as a wrapper for the actual test program.
The feature is in
Hello
How to add ATL support to my project?
I saw the question in the mailling list, but with no answer.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages
2009/6/11 elizabeta petreska elizabeta.petre...@gmail.com:
Hello
How to add ATL support to my project?
May be you can tell us what ATL is ?
A library?
Is it platform specific (MacOS, Windows, Unix...)?
The simplest way to do this is to give us a small intro to ATL
and/or providing us with a
On Thu, Jun 11, 2009 at 8:43 AM, elizabeta petreska
elizabeta.petre...@gmail.com wrote:
The ATL (Active Template Library) is project template in Visual Studio that
simplifies creation of COM objects.
http://en.wikipedia.org/wiki/Active_Template_Library
I was hoping that in Cmake exsist
On Tue, Jun 9, 2009 at 4:05 AM, Stefan Dröge ste...@sdroege.de wrote:
2009/6/9 Philip Lowman phi...@yhbt.com:
Yes, that is the only reason.
Can you try the CMakeFindEclipseCDT4.cmake attached to this bug report?
I've
wrapped the call to EXECUTE_PROCESS by saving the LANG environment
2009/6/11 elizabeta petreska elizabeta.petre...@gmail.com:
On Thu, Jun 11, 2009 at 8:43 AM, elizabeta petreska
elizabeta.petre...@gmail.com wrote:
The ATL (Active Template Library) is project template in Visual Studio
that simplifies creation of COM objects.
Hi everyone
I have a question concerning CDash. I have not tested it yet but I wonder how
are handled the dependencies between projects.
In projects that have a dependency on another project, I added a custom target
who does make in the other project directory.
Will the result of the
Great, now it works!
My CMakeLists.txt now looks like this:
cmake_minimum_required(VERSION 2.4)
project(hi CXX Fortran)
ADD_LIBRARY(hello SHARED hello.f90)
SET(TEST_SRCS test.cxx)
ADD_EXECUTABLE(hi ${TEST_SRCS})
TARGET_LINK_LIBRARIES(hi hello)
SET_TARGET_PROPERTIES(hi PROPERTIES
On Thu, Jun 11, 2009 at 8:55 AM, Eric Noulard eric.noul...@gmail.comwrote:
2009/6/11 elizabeta petreska elizabeta.petre...@gmail.com:
On Thu, Jun 11, 2009 at 8:43 AM, elizabeta petreska
elizabeta.petre...@gmail.com wrote:
The ATL (Active Template Library) is project template in
hello.
I've got a class in a folder that I want to run from a main.cpp file, when I
compile it, I get a undefined reference to the class's methods.
do I must create a lib from that single class in order to get the linking
working?
the CMakeList.txt looks like this:
ADD_LIBRARY(lib1 STATIC
Hi all:
I'm working on an embedded platform and building integrated software as
multimedia CE devices. And I am just started trying to introduce CMake to
replace my legacy environment constructed by many hand-written gnu styled
makefiles.
I have many components which is cross referred to
ADD_EXECUTABLE(prog main.cpp class.cpp)
On Thu, Jun 11, 2009 at 7:52 AM, e...@cs.bgu.ac.ile...@cs.bgu.ac.il wrote:
hello.
I've got a class in a folder that I want to run from a main.cpp file, when I
compile it, I get a undefined reference to the class's methods.
do I must create a lib from
On Thu 11 Jun 15:15 2009 Mike Jackson wrote:
ADD_EXECUTABLE(prog main.cpp class.cpp)
On Thu, Jun 11, 2009 at 7:52 AM, e...@cs.bgu.ac.ile...@cs.bgu.ac.il wrote:
hello.
I've got a class in a folder that I want to run from a main.cpp file, when
I compile it, I get a undefined reference
Philip Lowman wrote:
The feature is in CMake CVS (see ENVIRONMENT test property).
This came up at work the other day too, someone wanted to set the
LD_LIBRARY_PATH environment variable for some dlload()ed lua plugins as
part of a unit test. Given how popular this has become I think quite a
Chih-pin Wu wrote:
Hi all:
I'm working on an embedded platform and building integrated software
as multimedia CE devices. And I am just started trying to introduce
CMake to replace my legacy environment constructed by many hand-written
gnu styled makefiles.
I have many components which
On 11.06.2009, at 15:44, Bill Hoffman bill.hoff...@kitware.com wrote:
Chih-pin Wu wrote:
Hi all:
I'm working on an embedded platform and building integrated
software as multimedia CE devices. And I am just started trying to
introduce CMake to replace my legacy environment constructed by
Great, now it works!
My CMakeLists.txt now looks like this:
I would put everything in an executable, without an intermediate step with
ADD_LIBRARY. When I tested my suggestions for you on my computer, they
worked without any intermediate library. But you might have some other
project in mind,
Chih-pin Wu wrote:
Hi Bill:
Thanks, it's exactly what you mentioned, and I got some mistake on my
CMakeList.txt.
Originally I have some syntax like:
SET(LIB_DIRS ${LIB_DIRS} ${CMAKE_CURRENT_SOURCE_DIR}/../../../lib)
SET(LIBS ${LIBS} libMyLibA.a)
TARGET_LINK_LIBRARIES(${PROGNAME}
Done: http://public.kitware.com/Bug/view.php?id=9138
I also took David's advice and recreated my cdash project as qpid-cpp,
so I'm not affected by this problem at this time.
Thanks,
-Steve
-Original Message-
From: Julien Jomier [mailto:julien.jom...@kitware.com]
Sent: Thursday, June
Hi,
I need to know if, with the compiler option provided by the user, or
the default configuration of the system, the build produce 64 bit
binaries.
I can't see any obvious way to find that.
I need it (at least) to run java tests with the -d64 parameters, and
to add a /64 to the install
I'm having similar issues. Although I tried removing the \ or the
entire CMAKE_INTDIR=\Debug\, mentioned on this
http://www.mail-archive.com/cmake@cmake.org/msg16041.html post, but
it didn't make any difference.
This is what I get when I try to build a project that uses ATL
1Creating Type
kent williams wrote:
Interesting question. Looking at what we do (and that's based on what Slicer
does) the difference between 64 and 32 bit comes about in how we set the
CFLAGS and CXXFLAGS before we run CMake -- we don't tell CMake anything
about whether it's 32 or 64 bit.
I don't remember
And what if you are on a system like OS X where the default build is
32 bit but you can have a 64 bit binary built? Then
CMAKE_SIZEOF_VOID_P is going to be invalid.
---
Mike Jackson www.bluequartz.net
On Jun 11, 2009, at 2:06 PM, Bill Hoffman wrote:
kent williams wrote:
Michael Jackson wrote:
And what if you are on a system like OS X where the default build is 32
bit but you can have a 64 bit binary built? Then CMAKE_SIZEOF_VOID_P is
going to be invalid.
No, it is done with a try compile based on the current compiler settings.
-Bill
Michael Jackson wrote:
501:[mjack...@ferb:~]$ cd Desktop/
502:[mjack...@ferb:Desktop]$ mkdir Test
503:[mjack...@ferb:Desktop]$ cd Test; mkdir Build; cd Build
509:[mjack...@ferb:Build]$ cmake ../
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for
On Jun 11, 2009, at 3:09 PM, Bill Hoffman wrote:
Michael Jackson wrote:
501:[mjack...@ferb:~]$ cd Desktop/
502:[mjack...@ferb:Desktop]$ mkdir Test
503:[mjack...@ferb:Desktop]$ cd Test; mkdir Build; cd Build
509:[mjack...@ferb:Build]$ cmake ../
-- The C compiler identification is GNU
-- The
Michael Jackson wrote:
So it builds a 32 bit executable.
:)
Are you saying (from above) that if I have a 64 bit build of CMake then
I will get 64 bit binaries by default?
No, it depends on the flags given to the compiler. I think you want
-m64. So if you do this:
export CFLAGS=-m64
529:[mjack...@ferb:x64]$ export CXXFLAGS=-arch x86_64
530:[mjack...@ferb:x64]$ rm -rf *; cmake ../
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C
Le 11 juin 09 à 20:06, Bill Hoffman a écrit :
kent williams wrote:
Interesting question. Looking at what we do (and that's based on
what Slicer
does) the difference between 64 and 32 bit comes about in how we
set the
CFLAGS and CXXFLAGS before we run CMake -- we don't tell CMake
anything
I don't use that variable on Mac.
But it is still useful and sometimes needed for platforms that don't
support universal binaries.
Consider that Linux might have lib/ lib64/ and/or lib32/, and Windows
might have c:\program files\ and c:\program files (x86)\.
So find_library() and things like
Hi,
I am using CMake 2.6.4 with NSIS 2.4.5. and run into a problem when setting
CPACK_NSIS_MODIFY_PATH to ON (which forces the installer to show the dialog to
let the user decide whether or not to add the application directory to the
system PATH). This works fine, but I would like to know which
On 6/11/09 3:00 PM, Michael Jackson said:
-- CMAKE_SIZEOF_VOID_P: 4 THIS IS WRONG FOR X64 builds
Yeah, but gcc on 10.5 and earlier defaults to building 32 bit. If you
want 64 bit you need to pass '-arch x86_64' (or ppc64). Or in the case
of CMake, use CMAKE_OSX_ARCHITECTURES (or
TRY_COMPILE works fine for cross compiles, just not for *mutiple
configs/architectures simultaneously* compiles...
On Thu, Jun 11, 2009 at 3:41 PM, Sean McBride s...@rogue-research.comwrote:
On 6/11/09 3:00 PM, Michael Jackson said:
-- CMAKE_SIZEOF_VOID_P: 4 THIS IS WRONG FOR
Hello list!
As a learning exercise, I am adding CMake and CTest to a small open-
source library I made which currently has no build system:
http://hostilefork.com/nstate/
http://hostilefork.com/nocycle/
For the first step, I have been applying the configure_file
methodology
On Thu, Jun 11, 2009 at 11:32 PM, Hostile Forkhostilef...@gmail.com wrote:
Hello list!
As a learning exercise, I am adding CMake and CTest to a small open-source
library I made which currently has no build system:
http://hostilefork.com/nstate/
http://hostilefork.com/nocycle/
I have an executable that links with HDF5 (by the way, is there any
plan to create a FindHDF5.cmake file?).
The problem is that I have two flavors of libraries:
libhdf5_cpp.a libhdf5.a
libhdf5_cpp.dylib libhdf5.dylib
When I do
set( HDF5_LIBRARIES hdf5_cpp hdf5
On 6/11/09 5:25 PM, David Cole said:
TRY_COMPILE works fine for cross compiles, just not for *mutiple
configs/architectures simultaneously* compiles...
Thanks for the clarification, that language is clearer.
Does CMake detect and warn in such cases? (it is after all the common
case on OS X.)
On Thu, 2009-06-11 at 16:49 -0600, James C. Sutherland wrote:
I have an executable that links with HDF5 (by the way, is there any
plan to create a FindHDF5.cmake file?).
The problem is that I have two flavors of libraries:
libhdf5_cpp.a libhdf5.a
libhdf5_cpp.dylib
To the CMake developers:
The Visual Studio team has created a new blog to discuss the project system
in Visual Studio 2010:
http://blogs.msdn.com/vsproject/
This blog may contain information now and in the future that will help ease
the implementation of VS2010 support.
On Jun 11, 2009, at 4:49 PM, James C. Sutherland wrote:
I have an executable that links with HDF5 (by the way, is there any
plan to create a FindHDF5.cmake file?).
The problem is that I have two flavors of libraries:
libhdf5_cpp.a libhdf5.a
libhdf5_cpp.dylib
On Thu, Jun 11, 2009 at 5:05 PM, James C. Sutherland
james.sutherl...@utah.edu wrote:
On Jun 11, 2009, at 4:49 PM, James C. Sutherland wrote:
I have an executable that links with HDF5 (by the way, is there any plan
to create a FindHDF5.cmake file?).
The problem is that I have two flavors
If you are distributing your application on a Mac, then there are
myriads of methods to distribute the shared libraries with the
application.
James,
Can you point me in the right direction?
I haven't yet tried this on Linux, so I don't know what land mines
await me there...
Thanks,
Thanks. CMake really rocks!
2009/6/11 Bill Hoffman bill.hoff...@kitware.com
Philip Lowman wrote:
The feature is in CMake CVS (see ENVIRONMENT test property).
This came up at work the other day too, someone wanted to set the
LD_LIBRARY_PATH environment variable for some dlload()ed lua
James,
If you distribute on OS X then there are some CMake facilities to
help you create a stand alone .app bundle. Basically it will run
install_name_tool on the dylibs to make sure they reference
dependent libraries that are stored inside the .app bundle. Usually
this is a real pain to do by
http://www.bluequartz.net/cgi-bin/gitweb/gitweb.cgi?p=MXADataModel.git;a=blob;f=Resources/CMake/MXAFindHDF5.cmake;h=f96bf33a9d0efd42488752e6eec0124532e367ef;hb=6b6079cc30c62ac5a672c5a7a50c359af064fbe5
is a FindHDF5.cmake file that I also borrowed from the paraview
project, then added features
If you distribute on OS X then there are some CMake facilities to
help you create a stand alone .app bundle. Basically it will run
install_name_tool on the dylibs to make sure they reference
dependent libraries that are stored inside the .app bundle. Usually
this is a real pain to do by hand
On Thu, Jun 11, 2009 at 9:37 AM, Bill Hoffman bill.hoff...@kitware.comwrote:
Philip Lowman wrote:
The feature is in CMake CVS (see ENVIRONMENT test property).
This came up at work the other day too, someone wanted to set the
LD_LIBRARY_PATH environment variable for some dlload()ed lua
On Thu, Jun 11, 2009 at 8:46 PM, James C.
Sutherlandjames.sutherl...@utah.edu wrote:
If you distribute on OS X then there are some CMake facilities to
help you create a stand alone .app bundle. Basically it will run
install_name_tool on the dylibs to make sure they reference
dependent
On Jun 11, 2009, at 14:47 , Pau Garcia i Quiles wrote:
#define VAR_THAT_IS_ON @VAR_THAT_IS_ON@
#define VAR_THAT_IS_OFF @VAR_THAT_IS_OFF@
If you call CMake with 'cmake -DVAR_THAT_IS_ON=1 -DVAR_THAT_IS_OFF=0',
it will produce:
#define VAR_THAT_IS_ON 1
#define VAR_THAT_IS_OFF 0
Hello Pau,
Robert Dailey wrote:
To the CMake developers:
The Visual Studio team has created a new blog to discuss the project
system in Visual Studio 2010:
http://blogs.msdn.com/vsproject/
This blog may contain information now and in the future that will help
ease the implementation of VS2010 support.
Sometimes I'll do something like the following:
set (FOO_SOMETHING_SUPPORT 0)
OPTION (USE_SOMETHING blah blah ON)
if (USE_SOMETHING)
set (FOO_SOMETHING_SUPPORT 1)
endif()
then in my .h.in file I'll have:
#define FOO_SOMETHING_SUPPORT @ FOO_SOMETHING_SUPPORT@
That is just one way to do what
in your cmakelists.txt files use the following:
set (VAR_THAT_IS_ON 1)
set (VAR_THAT_IS_OFF 0)
instead of TRUE or FALSE. Means the same thing plus your configured
files will just work.
Mike
On Thu, Jun 11, 2009 at 5:32 PM, Hostile Forkhostilef...@gmail.com wrote:
Hello list!
As a learning
On Fri 12 Jun 1:14 2009 Hendrik Sattler wrote:
Am Donnerstag 11 Juni 2009 14:24:30 schrieb e...@cs.bgu.ac.il:
On Thu 11 Jun 15:15 2009 Mike Jackson wrote:
ADD_EXECUTABLE(prog main.cpp class.cpp)
actually, I've tried that but the program crashes instantly...
Then something is wrong in
53 matches
Mail list logo
