BIll,
>Kitware has not had the funding or access to a Fortran compiler that
works with VS 2010. So, that has not yet been implemented.
I've got two projects that are using fortran heavily, so I may have a go at
fixing up the generator.
If I were to spend a few days improving the fortran suppor
There was a bug where we were discussing keeping or ditching the version number
that gets appended to the CMake.app package. There are good reasons both to
keep it and to remove it. You may want to add your thoughts to the bug.
http://public.kitware.com/Bug/view.php?id=11693
___
On 2/21/2011 2:33 PM, Biddiscombe, John A. wrote:
First off, I just upgraded to cmake 2.8.4 (from 2.8.2) and the visual
studio + intel fortran support is much much better. Thank you whoever
fixed it up. Projects generate correctly and build out of the box
(Intel Fortran 10.x + visual studio 200
Hi Sean,
Thanks for the link,
After reading the link below, I think I will write a little script to delete
the symlinks and see if the install works, if not then I will
write another script to create them.
Alternatively after reading your second paragraph it may be better to rename
the installat
On Monday 21 February 2011, Schmid Alexander wrote:
...
> I did some tests and from my point of view you are right - I do not have to
> set it at all. But, nevertheless, the problem stays.
> The crosscompiling toolchain produces binary files with .out suffix, and
> for me it seems that the the TRY_
First off, I just upgraded to cmake 2.8.4 (from 2.8.2) and the visual studio +
intel fortran support is much much better. Thank you whoever fixed it up.
Projects generate correctly and build out of the box
(Intel Fortran 10.x + visual studio 2008) - previously I had to generate nmake
makefiles f
This should be fixed already in CMake's 'next' branch. If you can try
a nightly installer, or build yourself from 'next', let me know if
there is still any problem.
Fix will be in 2.8.5 when it comes out in a few months.
Thanks,
David
On Mon, Feb 21, 2011 at 12:39 PM, Allen D Byrne wrote:
> O
On 2/21/2011 12:16 PM, j s wrote:
LD_PRELOAD isn't that bad of a hack, actually. Intercepting open(),
read(), and possibly mmap() should cover most cases.
So
cl.exe /showincludes
doesn't work? According to this, it is available.
http://www.conifersystems.com/2008/10/09/dependencies
One more detail, this seems to be a problem only on non windows (non-make) -
windows VS machines ran the tests in correct declaration order.
Allen
> Bug reported:
> http://public.kitware.com/Bug/view.php?id=11877
>
>
> On Fri, Feb 18, 2011 at 10:30 AM, David Cole wrote:
> > Yup. ctest -N and
On Mon, Feb 21, 2011 at 1:29 AM, Jesper Eskilson wrote:
> On 02/19/2011 06:27 PM, Michael Wild wrote:
>
>> On 02/19/2011 06:16 PM, Jed Brown wrote:
>>
>>> On Fri, Feb 18, 2011 at 17:16, Michael Wild wrote:
>>>
>>> Well, cl.exe for one doesn't do this trick. This means, you'll have to
put it
David Cole skrev 2011-02-21 17:28:
SET_PROPERTY(GLOBAL PROPERTY USE_FOLDERS ${BUILD_USE_SOLUTION_FOLDERS})
ARGH! Of course. Thank you.
/Rob
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensourc
Robert Bielik skrev 2011-02-21 17:20:
Now next fun stuff. Since not everybody use VS2008 Pro (the express version
doesn't support solution folders :( ) I need to make this
an option:
OPTION(BUILD_USE_SOLUTION_FOLDERS "Enable grouping of projects in VS" OFF)
SET_PROPERTY(GLOBAL PROPERTY USE_FOL
Use:
SET_PROPERTY(GLOBAL PROPERTY USE_FOLDERS ${BUILD_USE_SOLUTION_FOLDERS})
On Mon, Feb 21, 2011 at 11:20 AM, Robert Bielik
wrote:
> David Cole skrev 2011-02-20 17:55:
>>
>> Those properties were first introduced in v2.8.3, that's why it didn't
>> do anything for 2.8.2...
>>
>
> Now next fun st
David Cole skrev 2011-02-20 17:55:
Those properties were first introduced in v2.8.3, that's why it didn't
do anything for 2.8.2...
Now next fun stuff. Since not everybody use VS2008 Pro (the express version
doesn't support solution folders :( ) I need to make this
an option:
OPTION(BUILD_USE
2011/2/21 Michael Wild :
>>> Do you know such a call can be configured?
>>> for example:
>>> export MYVARIABVLE=test; cd dir; compiler_call
>>
>> I don't think there is an easy way to do that from within CMake.
>> You would need some way to set env var "before" launching the compile rule
>> the on
On 02/21/2011 04:35 PM, Eric Noulard wrote:
> 2011/2/21 Łukasz Tasz :
>> 2011/2/21 Eric Noulard :
>>> What is your use case?
>>
>> In my case I'm making integration with ccache, and distcc, and as you
>> know all of them are tuned only via ENV_VARS.
>> Depending on CMAKE_BUILD_TYPE, compiler versio
2011/2/21 Łukasz Tasz :
> 2011/2/21 Eric Noulard :
>> What is your use case?
>
> In my case I'm making integration with ccache, and distcc, and as you
> know all of them are tuned only via ENV_VARS.
> Depending on CMAKE_BUILD_TYPE, compiler version, OS I would like to
> prepare correct DISTCC_HOSTS
On Sun, 20 Feb 2011 09:43:10 +1100, Andrew Maclean said:
>I am attempting to install this on Snow Leopard. The installation seems to
>work Ok but fails at the Install Command Line Tools stage, with the message:
>Failed create symlink installation may be incomplete: /usr/bin/ccmake
>... and so fort
2011/2/21 Eric Noulard :
>
> Since the makefiles are generated by CMake WHY do you need
> to define a "make" var?
>
> What do you want to do ?
>
> CMake was not designed to let you decide generator specifics things.
>
That's cool, I really like it, and in most cases it works fine e.g
CMAKE_VERBOSE
2011/2/21 Łukasz Tasz :
> Hi All,
>
> Could somebody help me how to provide own predefined make varibable from
> cmake configuration?
> Such a variable should be avaliable in the context of all generated
> makefiles.
Since the makefiles are generated by CMake WHY do you need
to define a "make" var
Dear All,
I'm trying to use the ExternalProject functionality. I'm under Microsoft
Windows 7 and using Microsoft Visual Studio 2010 with CMake 2.8.4. It's a
simple test, trying to compile some classes that need ITK, so I have an:
EXTERNALPROJECT_ADD(
ITK-ext
GIT_REPOSITORY "h
Hi All,
Could somebody help me how to provide own predefined make varibable from
cmake configuration?
Such a variable should be avaliable in the context of all generated
makefiles.
I would like to receive output in a way:
in master Makefile:
export MY_OWN_DEBUG_VAR="3"
MY_OWN_DEBUG_VAR should b
> -Ursprüngliche Nachricht-
> Von: David Cole [mailto:david.c...@kitware.com]
> Gesendet: Montag, 21. Februar 2011 13:41
> An: Schmid Alexander
> Cc: a.neundorf-w...@gmx.net; cmake@cmake.org
> Betreff: Re: [CMake] Cross-compiling: Cmake compiler and ABI check don´t work
> /
> TRY_COMPILE a
On Mon, Feb 21, 2011 at 2:14 AM, Schmid Alexander wrote:
> On Friday 18 February 2011, Schmid Alexander wrote:
>> Hi,
>>
>> of course, I´d like to have you think further about it, so here you go...
>
> ;-)
>
>> This is the toolchain file I use.
>> The specialty about is that I want to use the ARMC
24 matches
Mail list logo
