On 06/24/2011 12:32 AM, Todd Gamblin wrote:
> Thanks to Sean and Jed for useful counterexamples.
>
> A few more points:
>
> On Jun 23, 2011, at 8:50 AM, Michael Hertling wrote:
>
>> While I can understand your point, I'm of a different opinion: In the
>> end, it's the responsibility of the user
On 06/23/2011 06:20 PM, Jed Brown wrote:
> On Thu, Jun 23, 2011 at 17:50, Michael Hertling wrote:
>
>> You need to use a C99 compiler for your project
>
>
> This is already a problem. C99 introduces new keywords (e.g. restrict) and
> removes implicit int. It is entirely possible for part of a p
On 06/24/2011 04:16 PM, Owen Shepherd wrote:
> On 23/06/2011 23:32, "Todd Gamblin" wrote:
>> You could do this, but it seems like a lot of work for the developer AND
>> the user compared to my suggestion of just having a variable for the
>> compiler-specific C99 flags, or some similar mechanism.
Hi, I found that building inkscape with cairomm would fail because
cairommconfig.h could not be found (which cairomm.h includes),
Heres a 1 line patch to fix the problem.
Also reported bug, but not sure if its necessary.
http://cmake.org/Bug/view.php?id=12306
--
- Campbell
diff --git a/Modules/
(My point / question regarding documenting the variables passed by
find_package while operating in "Module" mode are still valid points /
questions. However, I think I've answered the musing further down the
emails.)
I just realized that PACKAGE_FIND_VERSION must be the actual variable
name pa
I was just noticing that the find_package command documentation talks
about how, in "Config" mode, the PACKAGE_FIND_* variables are defined
for use by the "-version.cmake" or
"Version.cmake" scripts for libraries. It further mentions
that when find_package is used in "Module" mode that the
"Find.
http://public.kitware.com/Bug/view.php?id=12304
I've added this bug, along with a patch to correct it.
Here is the patch:
--- ../../src.orig/cmake-2.8.4/Modules/FindSubversion.cmake
2011-02-15 14:51:41.0 -0600
+++ FindSubversion.cmake2011-06-24 11:27:49.38280 -0500
@@
On 23/06/2011 23:32, "Todd Gamblin" wrote:
>You could do this, but it seems like a lot of work for the developer AND
>the user compared to my suggestion of just having a variable for the
>compiler-specific C99 flags, or some similar mechanism. We know an awful
>lot of other things about compiler
I'll check my system, maybe cmake "can't find" MPI properly.
I'm using cmake 2.8.4. and my code works when I compile without cmake (I use
those instructions exactly).
Thank you
--- El jue, 23/6/11, Todd Gamblin escribió:
De: Todd Gamblin
Asunto: Re: [CMake] How to compile MPI code
Para: "Mª
Ah, that's a different problem. I believe you need to write a specific
toolchain file in your case, since your compiler creates binaries which does
not work on your own platform (?).
See e.g. here:
http://www.cmake.org/pipermail/cmake/2008-July/022868.html
Others might want to correct me if I'm
Doesn't work.. What I have is:
# export CC=i686-android-linux-gcc
# export CXX=i686-android-linux-gcc
<< skipped long paths to compiler >>
The C compiler "i686-android-linux-gcc" is not able to compile a
simple test program.
It fails with the following output: Change Dir: .../CMakeFile
11 matches
Mail list logo
