On 9/1/09 10:07 AM, Celil Rufat said:
>It appears that this is a bug with cmake, as it has been encountered
>elsewhere:
>
>Despite setting CMAKE_OSX_ARCHITECTURES as i386, cmake builds x86_64
>binaries on Snow Leopard, as default setting for gcc version 4.2.1 is
>now x86_64.
You may want to monit
Thanks for the suggestions.
It appears that this is a bug with cmake, as it has been encountered
elsewhere:
Despite setting CMAKE_OSX_ARCHITECTURES as i386, cmake builds x86_64
binaries on Snow Leopard, as default setting for gcc version 4.2.1 is
now x86_64.
http://www.cmake.org/pipermail/cmake/
Thanks a lot Brad for your inputs and suggestions. I got in touch with CGNS
team which use CMake and also I raised this issue with my own team...thanks
again.
Regards,
Venu
EMAILING FOR THE GREATER GOOD
Join me
> Date: Tue, 1 Sep 2009 11:58:31 -0400
> From: brad.k...@kitware.com
> To: gu
CMake seems to compile ok on HP/Linux ia64/Open64 compiler. Some tests
are failing:
http://www.cdash.org/CDash/viewTest.php?onlyfailed&buildid=415294
2cts
--
Mathieu
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://ww
venugopal gudimetla wrote:
>
>
> Hi Brad,
>
>>This brings us back to
>> my question: does the compiler identify itself with any documented
>> preprocessor symbol?
>
> I checked Absoft documentation and also asked Absoft support guys, there
> doesn't seem to be a pre-processor macro which identi
On Tuesday 01 September 2009 08:51:22 am Adolfo Rodríguez wrote:
> On Tue, Sep 1, 2009 at 4:49 PM, Clinton Stimpson
wrote:
> > Its already in cmake-gui.
> > Get the CVS version and you'll see it under Tools -> Show My Changes.
> > It'll give both -D command line arguments for cmake, and text you c
Hi,
This is what I call fast ...
Thank you!
I knew I requested that before but my impression was that nobody is really
interested in implementing it.
regards
Alin
On Tuesday 01 September 2009 15:49:23 you wrote:
> Its already in cmake-gui.
> Get the CVS version and you'll see it under Tools
On Tue, Sep 1, 2009 at 4:49 PM, Clinton Stimpson wrote:
>
> Its already in cmake-gui.
> Get the CVS version and you'll see it under Tools -> Show My Changes.
> It'll give both -D command line arguments for cmake, and text you can use
> for an initial cache file.
>
This is great!. There are quite
Its already in cmake-gui.
Get the CVS version and you'll see it under Tools -> Show My Changes.
It'll give both -D command line arguments for cmake, and text you can
use for an initial cache file.
Clint
On 09/01/2009 06:08 AM, Philip Lowman wrote:
Mod insightful +1
I would call it "Modified
On Tue, Sep 01, 2009 at 12:44:28AM -0700, bo...@email.arizona.edu wrote:
> I put ADD_TEST in my CMakeList.txt file. When I run ctest the results of the
> test are printed to the terminal.
>
> Is there a way to print a simple test message to the terminal?
Check the archives. This was discussed (e
John R. Cary wrote:
> BTW - should a 'CXX.cmake' file include *_C_FLAGS?
In principle no, but it works around some historical cruft
that hasn't been cleaned up yet.
> Curious about how these work. I assume that cmake does
> a mapping from the OS and compiler to a Platform file, but
> then there
On Tue, Sep 1, 2009 at 3:31 PM, John R. Cary wrote:
> Mathieu Malaterre wrote:
>>
>> On Tue, Sep 1, 2009 at 2:49 PM, Mathieu
>> Malaterre wrote:
>>
>>>
>>> On Tue, Sep 1, 2009 at 2:41 PM, Brad King wrote:
>>>
Mathieu Malaterre wrote:
>
> [ 4%] Built target cmsys
> Linkin
Mathieu Malaterre wrote:
On Tue, Sep 1, 2009 at 2:49 PM, Mathieu
Malaterre wrote:
On Tue, Sep 1, 2009 at 2:41 PM, Brad King wrote:
Mathieu Malaterre wrote:
[ 4%] Built target cmsys
Linking C shared module libcmsysTestDynload.so
/usr/lib/gcc/powerpc64-suse-linux/4.1.2/../../../.
_CMake_ isn't the one building the 32 bit binaries, 10.6 is building
them by default. You either have to rebuild all your support libraries
as 64 bit or Universal binaries, or figure out how to get your project
to build for 32 bit by supplying the CMAKE_OSX_ARCHITECTURES=i386.
You might wa
On Tue, Sep 1, 2009 at 2:49 PM, Mathieu
Malaterre wrote:
> On Tue, Sep 1, 2009 at 2:41 PM, Brad King wrote:
>> Mathieu Malaterre wrote:
>>> [ 4%] Built target cmsys
>>> Linking C shared module libcmsysTestDynload.so
>>> /usr/lib/gcc/powerpc64-suse-linux/4.1.2/../../../../lib/crt1.o:(.rodata+0x4):
On Tue, Sep 1, 2009 at 2:41 PM, Brad King wrote:
> Mathieu Malaterre wrote:
>> [ 4%] Built target cmsys
>> Linking C shared module libcmsysTestDynload.so
>> /usr/lib/gcc/powerpc64-suse-linux/4.1.2/../../../../lib/crt1.o:(.rodata+0x4):
>> undefined reference to `main'
>
> What does "make VERBOSE=1"
Mathieu Malaterre wrote:
> [ 4%] Built target cmsys
> Linking C shared module libcmsysTestDynload.so
> /usr/lib/gcc/powerpc64-suse-linux/4.1.2/../../../../lib/crt1.o:(.rodata+0x4):
> undefined reference to `main'
What does "make VERBOSE=1" say? Clearly this linker
line is missing the flag to mak
Mod insightful +1
I would call it "Modified Variables" though instead of "User View".
.. Original Message ...
On Tue, 1 Sep 2009 10:05:33 +0100 "Alin M Elena"
wrote:
>Hi,
>
>This issue was touched twice in the past
>http://www.cmake.org/pipermail/cmake/2009-April/thread.html#28419
>http:
Hi,
This issue was touched twice in the past
http://www.cmake.org/pipermail/cmake/2009-April/thread.html#28419
http://www.mail-archive.com/cmake@cmake.org/msg22904.html
Now I come with a feature proposal. I would like your comments on it before
adding it as an official feature request and maybe
Hi,
I'm trying to build a Mac OS X app bundle with private frameworks
embedded. Basically what I am using is like this:
find_library(SPARKLE_FRAMEWORK Sparkle ${ADD_FRAMEWORK_PATH})
set_source_files_properties(${SPARKLE_FRAMEWORK} PROPERTIES
MACOSX_PACKAGE_LOCATION Frameworks)
add_executabl
On Tue, Sep 1, 2009 at 10:56 AM, Mathieu
Malaterre wrote:
> On Thu, Aug 20, 2009 at 4:00 PM, Brad King wrote:
>> John R. Cary wrote:
>>> env CC=xlc_r CXX=xlC_r
>> [snip]
>>> -- The C compiler identification is GNU
>>
>> Be sure to create a fresh build tree when changing compilers.
>> CMake cached t
On Thu, Aug 20, 2009 at 4:00 PM, Brad King wrote:
> John R. Cary wrote:
>> env CC=xlc_r CXX=xlC_r
> [snip]
>> -- The C compiler identification is GNU
>
> Be sure to create a fresh build tree when changing compilers.
> CMake cached the 'cc' (gnu) compiler it found the first time
> and did not pay at
Hi everyone. I am a noob to cmake. Here is an easy question.
I put ADD_TEST in my CMakeList.txt file. When I run ctest the results of the
test are printed to the terminal.
Is there a way to print a simple test message to the terminal?
I see MESSAGE in the cmake documentation but that seems to
2009/8/31 Antonio Bulgheroni :
> Thanks a lot Eric. Installing 2.6.4 made the trick.
Ok fine.
> We should consider
> updating the wiki and saying that a newer version (than 2.6.0) is required
> for the component installation.
Good idea, since it's a Wiki may be you can do it yourself :-)
The 2.
On 1. Sep, 2009, at 6:47, King, Steven R wrote:
In case it's useful, here's a macro to copy an arbitrary file form
the source directory to the binary directory. The dependencies work
such that the file is not copied if the destination is up-to-date.
This is working fine for me, but sugges
On 1. Sep, 2009, at 4:12, j s wrote:
According to Microsoft, the math macros are not part of standard C/C+
+:
http://msdn.microsoft.com/en-us/library/4hwaceh6(VS.80).aspx
I'm not going to quibble with them on that point, as they were nice
enough
to provided them with:
_USE_MATH_DEFINES
as
26 matches
Mail list logo
