Am Dienstag, 16. November 2010 schrieb Eric Noulard:
> 2010/11/15 James Bigler
>
> > If I set a COMPILE_FLAGS property on a header file via
> > set_source_files_properties, CMake decides that these header files now
> > need to be compiled (i.e. not treated as header files).
> >
> > Is this the i
Hi David,
On Tuesday 16 November 2010 03:54:57 David Doria wrote:
> > You need INSTALL commands for everything you want to be in the package
> >
> > For your example:
> >
> > ADD_EXECUTABLE(DistanceBetweenPoints DistanceBetweenPoints.cxx)
> > INSTALL(TARGETS DistanceBetweenPoints DESTINATION bin
On Mon, Nov 15, 2010 at 05:57:04PM -0500, cmake-requ...@cmake.org wrote:
> Message: 2
> Date: Mon, 15 Nov 2010 16:37:05 -0500
> From: David Doria
> Subject: [CMake] CPack general question and example
> To: cmake@cmake.org
> Message-ID:
>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I
> You need INSTALL commands for everything you want to be in the package
>
> For your example:
>
> ADD_EXECUTABLE(DistanceBetweenPoints DistanceBetweenPoints.cxx)
> INSTALL(TARGETS DistanceBetweenPoints DESTINATION bin) # Add this for CPack
> to work
>
> Then both "make install" and "make package
2010/11/15 James Bigler
>
> If I set a COMPILE_FLAGS property on a header file via
> set_source_files_properties, CMake decides that these header files now need
> to be compiled (i.e. not treated as header files).
>
> Is this the intended behavior?
>
> I'm using both 2.8.1 and 2.8.3 on Windows w
On Mon, Nov 15, 2010 at 5:54 PM, David Cole wrote:
> On Mon, Nov 15, 2010 at 1:48 PM, Bill Hoffman
> wrote:
>> On 11/15/2010 1:36 PM, Dieter Oberkofler wrote:
>>>
>>> I'm having a hard time to understand why after upgrading from CMake 2.8.2
>>> to
>>> 2.8.3 I get "the input line is too long" whe
On Mon, Nov 15, 2010 at 1:48 PM, Bill Hoffman wrote:
> On 11/15/2010 1:36 PM, Dieter Oberkofler wrote:
>>
>> I'm having a hard time to understand why after upgrading from CMake 2.8.2
>> to
>> 2.8.3 I get "the input line is too long" when running nmake.
>> The problem must be related to the upgrade
If I set a COMPILE_FLAGS property on a header file via
set_source_files_properties, CMake decides that these header files now need
to be compiled (i.e. not treated as header files).
Is this the intended behavior?
I'm using both 2.8.1 and 2.8.3 on Windows with VS 2008 SP 1.
Thanks,
James
Hi Alex
Turned out the problem was the compiler I was using (gcc 4.5 is not
supported by Cuda on OSX). I switched compilers and 'add_executable(
foo.o)' works fine
Thanks.
Ted
___
Powered by www.kitware.com
Visit other Kitware open-source projec
> -Original Message-
> From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
> David Doria
> Sent: Monday, November 15, 2010 10:37 PM
> To: cmake@cmake.org
> Subject: [CMake] CPack general question and example
>
> I just heard about CPack and started playing with it
2010/11/15 David Doria :
> I just heard about CPack and started playing with it.
Which version of CMake/CPack are you using?
> I tried to make an RPM of a simple VTK program:
>
> http://www.cmake.org/Wiki/CMake/CPackExample
>
> When I run 'make package', I get an error:
>
> CPack Error: Problem c
I just heard about CPack and started playing with it. I tried to make
an RPM of a simple VTK program:
http://www.cmake.org/Wiki/CMake/CPackExample
When I run 'make package', I get an error:
CPack Error: Problem copying the package:
/home/doriad/CPackTest/bin/_CPack_Packages/Linux/RPM/DistanceBet
I'm trying to append a bunch of extra compile flags to a list of source
files:
set_property(SOURCE foo.cpp main.cpp APPEND PROPERTY COMPILE_FLAGS -Wall)
set( ignore_warning_flags
"-Wno-unused -Wno-switch -Wno-write-strings -Wno-strict-aliasing
-Wno-strict-prototypes -Wno-sign-compare" )
On 11/15/2010 1:36 PM, Dieter Oberkofler wrote:
I'm having a hard time to understand why after upgrading from CMake 2.8.2 to
2.8.3 I get "the input line is too long" when running nmake.
The problem must be related to the upgrade because moving back to 6.8.2 with
the absolute same build environmen
I'm having a hard time to understand why after upgrading from CMake 2.8.2 to
2.8.3 I get "the input line is too long" when running nmake.
The problem must be related to the upgrade because moving back to 6.8.2 with
the absolute same build environment works like a charm.
The error message seems to g
On Saturday 13 November 2010 20:43:12 Michael Hertling wrote:
> IIRC, the INSTALL() command with the FILES, PROGRAMS and DIRECTORY
> signature may appear in any CMakeLists.txt, but with the TARGETS
> signature, it must be placed in the same CMakeLists.txt as the
> targets it refers to. Anyway, IMO
On Monday 15 November 2010, Marek Szuba wrote:
> Hello,
>
> To begin with, a bit of background. The project which I've been
> converting to CMake depends on a certain binary-only library. This
> library is available in several versions, differing in what Fortran
> compiler has been used to produce
On Nov 15, 2010, at 12:29 PM, Oliver kfsone Smith wrote:
Michael Jackson said the following on 11/15/2010 9:33 AM:
I have been casually following this thread and I understand the OPs
hesitation when trying to add thousands of files into a CMake build
system but what I think one needs to th
On Mon, 15 Nov 2010 12:00:04 -0500
cmake-requ...@cmake.org wrote:
> How do you select which of the libraries to use? Based on your
> Fortran compiler?
To be exact, based on the Fortran compiler used to build the
binary-only library.
> If so, I would check for the CMAKE_Fortran_COMPILER_ID variabl
Michael Jackson said the following on 11/15/2010 9:33 AM:
I have been casually following this thread and I understand the OPs
hesitation when trying to add thousands of files into a CMake build
system but what I think one needs to think about is that you are only
going to add the files ONCE f
Eric Noulard said the following on 11/14/2010 4:00 AM:
I do (may be did?) have mental dichotomy between the "build process"
I'm going to take blame there for doing a poor job of posing the
original inquiry :)
But may be I shall step back and just think differently about it and even if
I need to
On 11/15/2010 04:40 PM, Marek Szuba wrote:
> Hello,
>
> To begin with, a bit of background. The project which I've been
> converting to CMake depends on a certain binary-only library. This
> library is available in several versions, differing in what Fortran
> compiler has been used to produce it;
Thanks,
I'd prefer that, but unfortunately, this is not possible atm.
On Tue, Nov 2, 2010 at 7:45 PM, David Cole wrote:
> Elminate the circularity. You'll drive yourself mad.
>
> :-)
>
>
> On Tue, Nov 2, 2010 at 2:38 PM, tmp
> wrote:
> > Hi all,
> >
> > I have got some circular dependencies in
On Sun, Nov 14, 2010 at 8:44 AM, Andreas Mohr wrote:
>
> However back to the question itself:
> to force a re-configure, one could "cmake -E touch"
> the CMAKE_CURRENT_LIST_FILE, somehow during target building
> or some such.
> This is quite certainly not the most direct (nor elegant!) way
> to f
Hello,
To begin with, a bit of background. The project which I've been
converting to CMake depends on a certain binary-only library. This
library is available in several versions, differing in what Fortran
compiler has been used to produce it; to make things simple let's
assume there are only two
On Nov 15, 2010, at 9:50 AM, Bill Hoffman wrote:
On 11/14/2010 5:00 AM, Eric Noulard wrote:
There has been some discussion on the list about improvement
of the dependency scanner, this kind of idea may be examined there.
May be it's worth filing a feature request on this subject.
I have no
On 11/14/2010 5:00 AM, Eric Noulard wrote:
There has been some discussion on the list about improvement
of the dependency scanner, this kind of idea may be examined there.
May be it's worth filing a feature request on this subject.
I have not followed this too closely. However, I thought mig
> -Original Message-
> From: Eric Noulard [mailto:eric.noul...@gmail.com]
> Sent: Monday, November 15, 2010 8:19 AM
> To: Vladislav Vaintroub
> Cc: CMake ML
> Subject: Re: [CMake] CPACK_MONOLITHIC_INSTALL not handled at runtime?
>
> 2010/11/14 Vladislav Vaintroub :
> Even if it's possi
On Sun, Nov 14, 2010 at 3:11 AM, Andreas Mohr wrote:
> On Thu, Nov 04, 2010 at 09:28:57AM -0400, cmake-requ...@cmake.org wrote:
>> Message: 1
>> Date: Thu, 4 Nov 2010 06:10:24 -0400
>> From: David Cole
>> Subject: Re: [CMake] Solution folder property does not work for
>> external projects i
29 matches
Mail list logo
