Dear cmake users,
I am having trouble in installing cmake on Linux (Red Hat Enterprise Linux
AS release 4, 2.6.9-42.ELsm) x86_64 machine. Till now I have installed
cmake on many occasion, but never faced such trouble.
I donot have root access to the cluster. So, I am installing it in
non-standard
On Fri, Oct 25, 2013 at 3:28 PM, Bill Hoffman wrote:
> On 10/25/2013 4:36 PM, James Bigler wrote:
>
>> My experience mirrored Clint's. Our version of CMake on the farm was at
>> 2.8.12, but locally developers were at differing versions. What made
>> matters worse is that it is a lot harder to di
On 10/25/2013 4:36 PM, James Bigler wrote:
My experience mirrored Clint's. Our version of CMake on the farm was at
2.8.12, but locally developers were at differing versions. What made
matters worse is that it is a lot harder to diagnose problems from farm
built binaries, so it wasn't until one
My experience mirrored Clint's. Our version of CMake on the farm was at
2.8.12, but locally developers were at differing versions. What made
matters worse is that it is a lot harder to diagnose problems from farm
built binaries, so it wasn't until one of the 4 developers looking into
this problem
On Friday, October 25, 2013 02:52:45 PM David Cole wrote:
> > Hmmm... Well that was a not backward compatible way of doing it.
>
> This behavior has existed for a long long time.
>
> Sorry for the extra effort you had to expend tracking down a mysterious
> problem because of this change. I remem
Hmmm... Well that was a not backward compatible way of doing it.
This behavior has existed for a long long time.
Sorry for the extra effort you had to expend tracking down a mysterious
problem because of this change. I remember having some discussions
(probably just verbal, though, I can't fi
Hmmm... Well that was a not backward compatible way of doing it. This
behavior has existed for a long long time.
Thanks for your help,
James
On Fri, Oct 25, 2013 at 10:58 AM, Nils Gladitz wrote:
> On 25.10.2013 18:42, James Bigler wrote:
>
>> When did CMake stop adding /STACK:1000 to the l
On 25.10.2013 18:42, James Bigler wrote:
When did CMake stop adding /STACK:1000 to the link line?
2.8.11:
http://public.kitware.com/Bug/view.php?id=12437
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
When did CMake stop adding /STACK:1000 to the link line?
I just spent several days trying to figure out why my code started failing
in strange ways, and I traced it down to this.
Thanks,
James
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://ww
Ralph Barth will be out of the office starting 25.10.2013 and will be
returning on 28.10.2013.
Ich werde Ihre Nachrichten nach meiner Rückkehr beantworten.
WLLM related questions pls. contact Sebastian Neusüß and Jens Keil.
Theo Price Feed from EDRE pls contact Jens Keil
There is our project here:
https://github.com/BRAINSia/NAMICExternalProjects
This is set up using the CMake 'SuperBuild' pattern first used with Slicer.
It might be more complicated a setup than you have in mind, but it builds
a large number of interdependent packages.
It's structured as a two-p
Clinton Stimpson wrote:
> I'm trying to point out that I did not get a warning when I was using
> cmake_minimum_required(VERSION 2.8)
> set_target_properties(mytarget PROPERTIES LINK_INTERFACE_LIBRARIES "")
> with
> CMake 2.8.12.
>
> That looks like a bug.
The policy warning is only issued if
On Friday, October 25, 2013 08:40:41 AM Stephen Kelly wrote:
> Clinton Stimpson wrote:
> > I have a target where I do this:
> > SET_TARGET_PROPERTIES(mytarget PROPERTIES LINK_INTERFACE_LIBRARIES "")
> > to hide 3rd party libraries from the link interface.
> >
> > When I do
> > if(APPLE)
> >
> >
13 matches
Mail list logo
