Is there a standard QUOTE type variable I can use to reference when
building compiler definitions that have quotes?
GNU make requires -DTARGETNAME="\"some text\""
watcom WMake requires -DTARGETNAME="some text"
___
Powered by www.kitware.com
Visit other
On Fri, Sep 10, 2010 at 1:06 PM, Alex G wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I have a project that I'm converting from plain ole' makefile to cmake.
> I need to have the build result be .ptx and .cubin (both, as the app
> attempts to read the .cubin first, and if it's incom
On Thursday 09 September 2010, Tim St. Clair wrote:
> For this chunk it only matters if I can decompose for *nix Makefiles.
Something like "ar x libfoo.a" should do.
Alex
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http:
On Wednesday 08 September 2010, Nick Foster wrote:
> Hi there,
>
> I'm using CMake with SDCC. Currently, support for SDCC in CMake does not
> also include dialects for its various assemblers. So I've created one, for
> the asx8051 assembler. The problem is that the asx8051 assembler shows
> nonstan
On Thursday 09 September 2010, David Aldrich wrote:
> Hi Michael
>
> > With CMake you can use absolute and relative paths, no problem. If you
> > use absolute paths, please use one of the pre-defined variables, such as
> > ${CMAKE_SOURCE_DIR}, ${CMAKE_BINARY_DIR}, ${CMAKE_CURRENT_SOURCE_DIR}
> > ${
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a project that I'm converting from plain ole' makefile to cmake.
I need to have the build result be .ptx and .cubin (both, as the app
attempts to read the .cubin first, and if it's incompatible with the GPU
architecture, assemble the .ptx file).
Part of the problem is that it's not clear if the user has built
boost-thread against pthreads or win32 threads. See the fix for #11121,
I've added a variable to control which threading library gets used if the
user crosscompiles boost-thread using a thread-api that isn't native on
their system.
On Fri, Sep 10, 2010 at 10:32 AM, David Doria wrote:
> On Fri, Sep 10, 2010 at 10:25 AM, David Cole
> wrote:
> > I think we're too close to the first release candidate of CMake 2.8.3 to
> be
> > adding features at this point.
> > But this is a great candidate for an early change immediately afte
2010/9/10 Michael Wild :
>> Does this also create dependencies on the multitude of header files
>> included by the .c files in SRCS (which would probably be desired in
>> case of the OP)?
>>
>> Ingolf
>
> No, it will not. But usually you have anyways something like:
>
> set(SRCS a.c b.c c.h d.c e.c
On 10. Sep, 2010, at 15:16 , Ingolf Steinbach wrote:
> 2010/9/10 Michael Wild :
>> set(SRCS a.c b.c d.c e.c)
>>
>> add_custom_command(OUTPUT ${CMAKE_BINARY_DIR}/f.c
>> COMMAND ...
>> DEPENDS ${SRCS}
>> COMMENT "Generating f.c"
>> VERBATIM)
>
> Does this also create dependencies on the multi
On Fri, Sep 10, 2010 at 10:25 AM, David Cole wrote:
> I think we're too close to the first release candidate of CMake 2.8.3 to be
> adding features at this point.
> But this is a great candidate for an early change immediately after the
> 2.8.3 release. If we get it into 'next' immediately after t
I think we're too close to the first release candidate of CMake 2.8.3 to be
adding features at this point.
But this is a great candidate for an early change immediately after the
2.8.3 release. If we get it into 'next' immediately after the upcoming
release, then all the kinks (there will be one o
The problem wasn't related to the universal binaries, but to the SDK used
(10.5). I need to add "-mmacosx-version-min=10.5" to the compiler flags in
order to make it work.
Shouldn't this be handled automatically by CMake?
On Fri, Sep 10, 2010 at 8:46 AM, Pedro d'Aquino wrote:
> Hi everyone,
>
>
2010/9/10 Michael Wild :
> set(SRCS a.c b.c d.c e.c)
>
> add_custom_command(OUTPUT ${CMAKE_BINARY_DIR}/f.c
> COMMAND ...
> DEPENDS ${SRCS}
> COMMENT "Generating f.c"
> VERBATIM)
Does this also create dependencies on the multitude of header files
included by the .c files in SRCS (which would pr
Hi David,
Thank for your information. Indeed the CMAKE_SOURCE_DIR differs.
This gave me a new lead. Following your hint allowed me to compile
the executable, however linking to "a_compiled_lib" was causing
a new problem.
So I've decided to solve the problem differently. Namely by
moving the "add_
Hi everyone,
I'm volunteering to become the primary maintainer of FindBoost.cmake.
--
Philip Lowman
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-t
> OK... good. I was just clarifying for the readers of the thread why we will
> not be "auto-configuring-for-multiple-iterations"... Ever. :-)
>
Ok, so is the voting over? There didn't seem to be much participation
(as expected...). Where does it go from here?
David
__
On 09/08/2010 05:47 AM, Marcel Loose wrote:
> I would like to inform you that I'm volunteering to become the
> maintainer of FindSubversion.cmake.
Thanks! I've updated the wiki page to credit your role:
http://www.cmake.org/Wiki/CMake:Module_Maintainers
It looks like your cmake.git "next" acc
Hi everyone,
I'm currently modifying an existing CMake-based project to build universal
binaries on 10.6.4. Xcode 3.2.3 builds the new project fine, but the
make-based compilation fails because of an undefined symbol,
__Unwind_Resume.
The actual command used for compiling each C++ file is (from V
That's great. Thanks for your patience!
David
> -Original Message-
> From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf
> Of Michael Wild
> Sent: 10 September 2010 12:30
> To: David Aldrich
> Cc: cmake@cmake.org
> Subject: Re: [CMake] Question about add_custom_comman
Print out the value of CMAKE_SOURCE_DIR in your CMakeLists.txt file... It's
different in the context of your outer project and your test project.
If it's "/my/proj" for your outer project, it's going to be "/my/proj/test"
in your test project.
Is there a directory named "/my/proj/test/include1"?
On 10. Sep, 2010, at 12:38 , David Aldrich wrote:
> Hi Michael
>
> Thanks for your help. Please see question below.
>
>> CMAKE_MINIMUM_REQUIRED(VERSION 2.8 FATAL_ERROR)
>> PROJECT(GENDEP C)
>> FILE(WRITE ${CMAKE_BINARY_DIR}/g.c "void g(void){}\n")
>> ADD_CUSTOM_COMMAND(
>>OUTPUT ${CMAKE_BIN
Hi Michael
Thanks for your help. Please see question below.
> CMAKE_MINIMUM_REQUIRED(VERSION 2.8 FATAL_ERROR)
> PROJECT(GENDEP C)
> FILE(WRITE ${CMAKE_BINARY_DIR}/g.c "void g(void){}\n")
> ADD_CUSTOM_COMMAND(
> OUTPUT ${CMAKE_BINARY_DIR}/f.c
> COMMAND echo "void f(void){}" > ${CMAKE_BINAR
On 09/09/2010 09:21 PM, John Drescher wrote:
> Do not do that. Your application will crash (in unexpected ways) if
> you mix debug and release libraries in visual studio. You also can not
> mix compiler versions.
I mix release/debug libraries all the time. Just because I wish to debug
my applicati
On 9. Sep, 2010, at 17:43 , KSpam wrote:
> Benjamin,
>
>> Thank you for your quick answer. I had a quick glance - what I don't
>> quite understand is how can I integrate this into my custom cmake
>> script? I have a ADD_CUSTOM_COMMAND, and in the depends I need this list
>> of dependent files (t
Hi Justin
Thank you for the input. I think that's actually a doable solution, even
though performance would probably suck. But still, better than having
bugs in the system.
Thanks
Benjamin
On 09/09/2010 05:43 PM, KSpam wrote:
> Benjamin,
>
>> Thank you for your quick answer. I had a quick glanc
Hello,
I try to accomplish to add a test, that compiles and runs afterward.
For the test that I want to run I have defined a project
CMakeLists.txt project in
${CMAKE_SOURCE_DIR}/test/, which looks like:
project(test_tgt)
cmake_minimum_required(VERSION 2.6)
include_directories(${CMAKE_SO
27 matches
Mail list logo
