On Tuesday 10 October 2006 23:20, Sean McBride wrote:
> On 2006-10-10 21:47, Axel Roebel said:
...
> I'm pretty sure there is no way to specify per-architecture variants of
> these things. I believe this was discussed in bug 2492, which you may
> want to read (its long).
Thanks, I've read that. B
On 2006-10-10 21:47, Axel Roebel said:
>I am creating universal binaries by means of
>compilation on different (ppc and intel) machines
>and later combining the results using lipo.
>
>For maximum backwards compatibility I need to
>set the environment variable
>
> MACOSX_DEPLOYMENT_TARGET=10.3
>
>o
At 04:56 PM 10/10/2006, Sean McBride wrote:
>Hi all,
>
>If I make just one change (CMAKE_GENERATOR from "Unix Makefiles" to
>"Xcode") CMake won't build, giving this error:
>
>-- Check for working C compiler: gcc
>-- Check for working C compiler: gcc -- broken
>CMake Error: Error in cmake code at
>/
On 10/10/06 4:56 PM, "Brad King" <[EMAIL PROTECTED]> wrote:
> Mike Jackson wrote:
>> On 10/10/06 4:08 PM, "Brad King" <[EMAIL PROTECTED]> wrote:
>>> cmake --help-command SET_TARGET_PROPERTIES
>>
>> OK.. Reading all the output from that command there seems to be some
>> mutually exclusive setti
Hi all,
If I make just one change (CMAKE_GENERATOR from "Unix Makefiles" to
"Xcode") CMake won't build, giving this error:
-- Check for working C compiler: gcc
-- Check for working C compiler: gcc -- broken
CMake Error: Error in cmake code at
/usr/local/cmake/share/CMake/Modules/CMakeTestCCompile
Mike Jackson wrote:
> On 10/10/06 4:08 PM, "Brad King" <[EMAIL PROTECTED]> wrote:
>> cmake --help-command SET_TARGET_PROPERTIES
>
> OK.. Reading all the output from that command there seems to be some
> mutually exclusive settings. Also, the output has settings like
> INSTALL_NAME_DIR, should thos
On 10/10/06 4:08 PM, "Brad King" <[EMAIL PROTECTED]> wrote:
> Mike Jackson wrote:
>> I am attempting to set the "install_name" on OS X for Shared Libraries but
>> the solution that I _thought_ would work does not because somewhere in cmake
>> the linker flag "-install_name" is _already_ defined an
Kedzierski, Artur CIV NAVSURFWARCENDIV CORONA wrote:
> Is this part of CMake 2.4.3?
> I get this error:
> INSTALL called with unknown mode DIRECTORY
It is in CVS CMake. It will be in 2.4.4.
-Brad
___
CMake mailing list
CMake@cmake.org
http
Mike Jackson wrote:
> I am attempting to set the "install_name" on OS X for Shared Libraries but
> the solution that I _thought_ would work does not because somewhere in cmake
> the linker flag "-install_name" is _already_ defined and so adding another
> one just confuses the linker.
> Is there s
Is this part of CMake 2.4.3?
I get this error:
INSTALL called with unknown mode DIRECTORY
--
Artur Kedzierski
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Filipe Sousa
Sent: Tuesday, October 10, 2006 9:50
To: CMake Mailing Lis
Kedzierski, Artur CIV NAVSURFWARCENDIV CORONA wrote:
> I am looking at the readme.txt file in CMake's modules
> directory. It says:
>
> Please use the following consistent variable names for general use.
> XXX_INCLUDE_DIRS
> ...
> You do not have to provide all of the above variables. You
I am attempting to set the "install_name" on OS X for Shared Libraries but
the solution that I _thought_ would work does not because somewhere in cmake
the linker flag "-install_name" is _already_ defined and so adding another
one just confuses the linker.
Is there some way I can hack a .cmake fi
Hi,
in my cmake projects I support mac os x and
I am creating universal binaries by means of
compilation on different (ppc and intel) machines
and later combining the results using lipo.
For maximum backwards compatibility I need to
set the environment variable
MACOSX_DEPLOYMENT_TARGET=10.3
on
Pecevski Dejan wrote:
> Hi,
>
> As part of our build process which uses cmake, we want to generate
> wrapper c++ files from existing sources, for python interfacing (using
> Py++ and boost.python).
> The dependency we want to achieve is :
> A1.cpp A2.cpp A3.cpp A1.h A2.h A3.h ... <-
Hi,
As part of our build process which uses cmake, we want to generate
wrapper c++ files from existing sources, for python interfacing (using
Py++ and boost.python).
The dependency we want to achieve is :
A1.cpp A2.cpp A3.cpp A1.h A2.h A3.h ... <- Abase.h generate.py
wrapLibrary
Hi,
I am looking at the readme.txt file in CMake's modules
directory. It says:
Please use the following consistent variable names for general use.
XXX_INCLUDE_DIRS
...
You do not have to provide all of the above variables. You should
provide [...] XXX_INCLUDE_DIR [...]
Em Terça 10 Outubro 2006 15:03, Brad King escreveu:
> Helio Chissini de Castro wrote:
> > Hi everyone
> >
> > Is there an easy way to make a different install prefix durong the
> > install phase, most directed for RPM construction ( like the old DESTDIR
> > on auto*tools ) ?
> > I have a code that
Helio Chissini de Castro wrote:
> Hi everyone
>
> Is there an easy way to make a different install prefix durong the install
> phase, most directed for RPM construction ( like the old DESTDIR on
> auto*tools ) ?
> I have a code that during build parse and substitute de real install prefix,
> an
Hi everyone
Is there an easy way to make a different install prefix durong the install
phase, most directed for RPM construction ( like the old DESTDIR on
auto*tools ) ?
I have a code that during build parse and substitute de real install prefix,
and if i set CMAKE_INSTALL_PREFIX pointing to rp
Kedzierski, Artur CIV NAVSURFWARCENDIV CORONA wrote:
> Lets say I have this dir structure:
> include/a/a1.h
> include/a/a2.h
> include/b/b1.h
> include/c/c1/c1.h
> When I do this:
> FILE(GLOB_RECURSE INSTALL_HEADERS RELATIVE "${CMAKE_SOURCE_DIR}"
> "$(CMAKE_SOURCE_DIR}/include/*.h")
> I
There is UsePkgConfig.cmake in CMake distribution
that can parse the pkgconfig for you. However, I don't
know if it removes the end of line characters.
--
Artur Kedzierski
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
frederic heem
Sent: Tuesday
Lets say I have this dir structure:
include/a/a1.h
include/a/a2.h
include/b/b1.h
include/c/c1/c1.h
When I do this:
FILE(GLOB_RECURSE INSTALL_HEADERS RELATIVE "${CMAKE_SOURCE_DIR}"
"$(CMAKE_SOURCE_DIR}/include/*.h")
INSTALL(FILES ${INSTALL_HEADERS} DESTINATION include)
I get
Hello Alan,
A#1:
You can overwrite several aspects of NSIS installer. You can look in
CMake/Modules/NSIS.template.in. If you want to do something even more
complicated, you can even overwrite NSIS.template.in by placing a file
with that name in your Source tree and then when running cpack add
Thanks. The key was a clean build tree.
From: Brad King <[EMAIL PROTECTED]>
To: Toni Cebrian <[EMAIL PROTECTED]>
CC: cmake@cmake.org
Subject: Re: [CMake] Problems selecting compiler in Solaris
Date: Tue, 10 Oct 2006 09:02:38 -0400
Toni Cebrian wrote:
>I have a Sparc machine with Solaris 8
frederic heem wrote:
> The output of pkgconfig has to be parsed to make it compatible with cmake.
> pkgconfig adds the end of line for each results.
> Is there a portable way to remove the end of line ?
Look at STRING(REGEX)
-Brad
___
CMake mailing list
Hi,
The output of pkgconfig has to be parsed to make it compatible with cmake.
pkgconfig adds the end of line for each results.
Is there a portable way to remove the end of line ?
Fred
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/li
At 05:57 AM 10/10/2006, John Biddiscombe wrote:
>Matthieu
>
>If you have qt3 and qt4 that is not in your path, it should all work if you do
>the following
>run ccmake, it will detect qt3, now set desired qt to 4, run ccmake again.
>some errors no doubt. Force cmake's qmake setting to point to
>/
Mike Jackson wrote:
> I just tried to have CMake generate a "debug" build of my project but when
> cmake ran it gave me the warning that Cmake was forcing my build type to
> Release since that is what VTK was built with. I _understand_ the error. What
> I need to know is if there is a way to ac
Toni Cebrian wrote:
>I have a Sparc machine with Solaris 8 installed. I have locally
> installed GCC (/usr/local/bin) and mounted with NFS a disk with the
> compiler tools of Sun (/opt/studio11/SUNWspro/bin). The problem I have
> is that when I run ccmake I try to select the compiler of Sun
> (
At 05:43 AM 10/10/2006, Toni Cebrian wrote:
>Hello,
>
> I have a Sparc machine with Solaris 8 installed. I have locally installed
> GCC (/usr/local/bin) and mounted with NFS a disk with the compiler tools of
> Sun (/opt/studio11/SUNWspro/bin). The problem I have is that when I run
> ccmake I t
Matthieu
If you have qt3 and qt4 that is not in your path, it should all work if
you do the following
run ccmake, it will detect qt3, now set desired qt to 4, run ccmake
again. some errors no doubt. Force cmake's qmake setting to point to
/my/path/of/stuff/qt-4.x.0/bin/qmake, now delete all ot
Hello,
I have a Sparc machine with Solaris 8 installed. I have locally
installed GCC (/usr/local/bin) and mounted with NFS a disk with the compiler
tools of Sun (/opt/studio11/SUNWspro/bin). The problem I have is that when I
run ccmake I try to select the compiler of Sun
(/opt/studio11/SUN
Hi,
I have some question about how CPack works under windows.
Firstly, how can I control NSIS with CPack to allow the choice of installing
some sub packages ?
Secondly, in the case of Visual Studio, I don't have the target for building
the source package !
How can I have the package for th
33 matches
Mail list logo
