On 14 Feb 2013, at 18:58, HB-GRAL flightg...@sablonier.ch wrote:
With simple -DCMAKE_INSTALL_PREFIX it finds the custom location of the
headers and libs without any other option, but when I add
-DSIMGEAR_INCLUDE_DIR=/path/to/include it takes the headers from this
location, but not the
Hi James
Thanks, yes, am aware of this kind of separation. But I thought: Why does
cmake configuration make it possible to link against an osg include and lib dir
for every part, while simgear has only a an option for headers and not the libs
?. And then when you set the simgear include dir,
On Fri, 15 Feb 2013 08:48:59 +, James wrote in message
954f9f95-7614-4c0e-a82f-3b589fa4e...@mac.com:
On 14 Feb 2013, at 18:58, HB-GRAL flightg...@sablonier.ch wrote:
With simple -DCMAKE_INSTALL_PREFIX it finds the custom location
of the headers and libs without any other option, but
On Friday, November 23, 2012 14:33:58 Renk Thorsten wrote:
I'm just trying to get a working devel environment on my new machine, and
I've succeeded in compiling simgear, but flightgear refuses the cmake
configuration. Basically I want to have the simgear libs inside a user
directory and not
On Fri, 2012-11-23 at 12:33 +, Renk Thorsten wrote:
cmake ../../flightgear -DSIMGEAR_DIR:PATH=/home/fgfs/FGLib
Hi,
Try -
$ export SIMGEAR_DIR=/home/fgfs/FGLib \
cmake ../../flightgear
In FG/CMakeModules/FindSimGear.cmake you will find
HINTS $ENV{SIMGEAR_DIR}
Note the 'ENV', so it
On 23 Nov 2012, at 12:33, Renk Thorsten wrote:
When I change to my flightgear build directory and do
cmake ../../flightgear
Use the same CMAKE_INSTALL_PREFIX for everything, and it will all work out. No
need to set SIMGEAR_DIR or anything. If you *have* set SIMGEAR_DIR or other
If you *have* set SIMGEAR_DIR or other settings, I'd recommend erasing your
build
directory and running cmake from clean - it 'remembers' previous values in
the build dir's cache.
Ah, that's how it's supposed to be... I've now hacked my way through by adding
the path explicitly to
On Wed, 2012-02-08 at 11:35 +, Jon Stockill wrote:
I'm currently updating some jenkins build scripts for cmake rather than
autoconf, and I'm having problems getting the build to link against
local copies of all the dependencies. Is there a simple way of
specifying where to look for
Hi,
There is a shortcut if dependencies and results are all in the same directory
prefix:
-DCMAKE_INSTALL_PREFIX=directory
This may not be suitable for jenkins.
Olaf Flebbe
o...@oflebbe.de
Am 08.02.2012 um 12:35 schrieb Jon Stockill:
I'm currently updating some jenkins build scripts for
I have added the path for SIMGEAR_INCLUDE_DIR, and now the error message is:-
looking for static Simgear libraries
looking for version: 2.5.0
CMake Error at C:/Program Files (x86)/CMake
2.8/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:91 (MESSAGE):
Could NOT find SimGear
Problem solved, and sorry for the noise.
I had forgotten to change CMAKE_INSTALL_PREFIX when configuring simgear.
Alan
From: Alan Teeder
Sent: Tuesday, December 20, 2011 1:29 PM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Cmake windows
I have added the path
Hi,
I updated README.cmake with Windows instructions. Could a native English
speaker review my spelling and grammar ?
Regards,
-Fred
--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
Thanks Fred.
It looks fine.
Alan (who failed his French O Level exams 3 times!)
-Original Message-
From: Frederic Bouvier
Sent: Friday, November 11, 2011 1:08 PM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] cmake
Hi,
I updated README.cmake with Windows
On Mon, 2011-11-07 at 18:26 +, James Turner wrote:
On 7 Nov 2011, at 17:07, Martin Spott wrote:
Ok, I conclude: LIB_POSTFIX im Simgear doesn't work as expected ;-/
I think we have a 'thinko' in the module - looking at the code, we're using:
install (TARGETS ${libName} ARCHIVE
On Tue, 08 Nov 2011 10:03:42 +0100, Erik wrote in message
1320743022.2034.0.camel@Raptor:
On Mon, 2011-11-07 at 18:26 +, James Turner wrote:
On 7 Nov 2011, at 17:07, Martin Spott wrote:
Ok, I conclude: LIB_POSTFIX im Simgear doesn't work as
expected ;-/
I think we have a
On Tue, 2011-11-08 at 11:07 +0100, Arnt Karlsen wrote:
On Tue, 08 Nov 2011 10:03:42 +0100, Erik wrote in message
IF(CMAKE_SIZEOF_VOID_P MATCHES 8)
SET(LIB_POSTFIX 64 CACHE STRING suffix for 32/64 dir placement)
MARK_AS_ADVANCED(LIB_POSTFIX)
ENDIF()
IF(NOT DEFINED LIB_POSTFIX)
On Tue, 08 Nov 2011 11:15:50 +0100, Erik wrote in message
1320747350.5635.0.camel@Raptor:
On Tue, 2011-11-08 at 11:07 +0100, Arnt Karlsen wrote:
On Tue, 08 Nov 2011 10:03:42 +0100, Erik wrote in message
IF(CMAKE_SIZEOF_VOID_P MATCHES 8)
SET(LIB_POSTFIX 64 CACHE STRING suffix for
Jon Stockill wrote:
On 04/11/11 00:00, Martin Spott wrote:
Jon Stockill wrote:
Simgear doesn't seem to install to the correct directory on 64 bit
systems any more - there doesn't seem to be any way to tell it to use
/usr/lib64 instead of /usr/lib
That's in LIB_POSTFIX. Try:
# ~ cmake
On 7 Nov 2011, at 17:07, Martin Spott wrote:
Ok, I conclude: LIB_POSTFIX im Simgear doesn't work as expected ;-/
I think we have a 'thinko' in the module - looking at the code, we're using:
install (TARGETS ${libName} ARCHIVE DESTINATION lib${LIB_SUFFIX})
... my guess is if this was
Am 05.11.11 03:27, schrieb Roland Häder:
On Sat, 2011-11-05 at 01:31 +0100, HB-GRAL wrote:
Hi James
I successfully built simgear/flightgear today with cmake 2.8.4 and OSX
10.6.8. There have been some small changes I added to CMakeLists for
sg/fg: SET(CMAKE_CXX_FLAGS -arch i386) and
On 5 Nov 2011, at 11:25, HB-GRAL wrote:
Maybe how to set this flags for OSX should go to the readme once. I
think some OSX users will end up with linking errors because simgear
compiles well with x86_64, but then you run into a lot of problems
trying to compile flightgear, on OSX. Btw. I
Am 05.11.11 17:13, schrieb James Turner:
On 5 Nov 2011, at 11:25, HB-GRAL wrote:
Maybe how to set this flags for OSX should go to the readme once. I
think some OSX users will end up with linking errors because simgear
compiles well with x86_64, but then you run into a lot of problems
trying
Am 05.11.11 20:25, schrieb HB-GRAL:
Am 05.11.11 17:13, schrieb James Turner:
On 5 Nov 2011, at 11:25, HB-GRAL wrote:
Maybe how to set this flags for OSX should go to the readme once. I
think some OSX users will end up with linking errors because simgear
compiles well with x86_64, but then
Am 05.11.11 20:46, schrieb HB-GRAL:
Am 05.11.11 20:25, schrieb HB-GRAL:
Am 05.11.11 17:13, schrieb James Turner:
On 5 Nov 2011, at 11:25, HB-GRAL wrote:
Maybe how to set this flags for OSX should go to the readme once. I
think some OSX users will end up with linking errors because simgear
On 4 Nov 2011, at 00:41, Jon Stockill wrote:
I believe it's FG_DATA_DIR, as observed here:
https://gitorious.org/fg/flightgear/commit/4b8ef9c3cf4f4f3565de3678cd733ad8067be6d9
Thanks - that worked (well, it returns the correct details when you run
cmake with that option, I've yet to test
On 3 Nov 2011, at 23:05, Jon Stockill wrote:
There's doesn't seem to be any way to enable the jpg-httpd server.
(Under autoconf it was enabled by default if Simgear was built with jpeg
factory support).
-DJPEG_FACTORY=1
... except, hmm, that only seems to exist for Simgear let me
Hi James,
On 4 Nov 2011, at 00:41, Jon Stockill wrote:
I believe it's FG_DATA_DIR, as observed here:
https://gitorious.org/fg/flightgear/commit/4b8ef9c3cf4f4f3565de3678cd733ad8067be6d9
Thanks - that worked (well, it returns the correct details when you
run
cmake with that
On Sat, 2011-11-05 at 01:31 +0100, HB-GRAL wrote:
Hi James
I successfully built simgear/flightgear today with cmake 2.8.4 and OSX
10.6.8. There have been some small changes I added to CMakeLists for
sg/fg: SET(CMAKE_CXX_FLAGS -arch i386) and SET(CMAKE_C_FLAGS -arch
i386). I am sure there
Jon Stockill wrote:
Simgear doesn't seem to install to the correct directory on 64 bit
systems any more - there doesn't seem to be any way to tell it to use
/usr/lib64 instead of /usr/lib
That's in LIB_POSTFIX. Try:
# ~ cmake -D CMAKE_INSTALL_PREFIX=/usr -D LIB_POSTFIX=64 [...]
Cheers,
On Friday, November 04, 2011 01:05:25 Jon Stockill wrote:
Have we changed the default data directory again? cmake outputs this:
-- Using default data-dir: /usr/lib/FlightGear
There doesn't appear to be any way to set it within ccmake or from te
commandline.
I believe it's FG_DATA_DIR, as
On 04/11/11 00:00, Martin Spott wrote:
Jon Stockill wrote:
Simgear doesn't seem to install to the correct directory on 64 bit
systems any more - there doesn't seem to be any way to tell it to use
/usr/lib64 instead of /usr/lib
That's in LIB_POSTFIX. Try:
# ~ cmake -D
On 04/11/11 00:08, Adrian Musceac wrote:
On Friday, November 04, 2011 01:05:25 Jon Stockill wrote:
Have we changed the default data directory again? cmake outputs this:
-- Using default data-dir: /usr/lib/FlightGear
There doesn't appear to be any way to set it within ccmake or from te
Hi Mathias,
Thanks again for your reply, comments and
suggestions... always very welcome and all taken
constructively. And I hope you understand
I am NOT the one just saying it 'does not work'...
I _AM_ taking the time, trying to understand,
HOW to make the windows cmake GUI work better...
Geoff
I found the Windows Cmake procedure rather simpler than you (but still much
more complicated than the simple Flightgear single MSVC project).
Here again is the recipe, from my post of 18 Oct, to which you can add my
now infamous step 12a from 19 Oct.
Alan
1. Set up a work directory
Hi,
On Friday, October 28, 2011 20:20:55 Geoff McLane wrote:
Re: In Windows (XP WIN32) - using CMake GUI
=
Unfortunately, here not so good ;=(( for building
FG. SG was not too bad...
As mentioned, I had to add two options,
PTW32_STATIC_LIB, to use pthreads (for
On Sat, 2011-10-29 at 13:49 +0200, Mathias Fröhlich wrote:
Hi,
On Friday, October 28, 2011 20:20:55 Geoff McLane wrote:
Re: In Windows (XP WIN32) - using CMake GUI
=
Unfortunately, here not so good ;=(( for building
FG. SG was not too bad...
As
Hi Geoff,
On Saturday, October 29, 2011 18:21:29 Geoff McLane wrote:
Thank you for your reply and ideas... and
hope I can answer some things regarding Windows...
And as usual, sorry in advance that this is so
long...
So, my disclaimer is that I do not have any win32 system running.
I just
On 26 Oct 2011, at 19:24, Geoff McLane wrote:
Maybe, as you have suggested, this is over kill,
setting BOTH SIMGEAR_DIR in the environment,
AND passing SIMGEAR_INCLUDE_DIR to cmake,
and when I feel comfortable, I will eliminate
one or the other for further testing...
BUT now I have
On Fri, 2011-10-28 at 08:57 +0100, James Turner wrote:
On 26 Oct 2011, at 19:24, Geoff McLane wrote:
Maybe, as you have suggested, this is over kill,
setting BOTH SIMGEAR_DIR in the environment,
AND passing SIMGEAR_INCLUDE_DIR to cmake,
and when I feel comfortable, I will eliminate
Geoff
I hope James listens to you, I have been studiously ignored.
Alan
-Original Message-
From: Geoff McLane
Sent: Friday, October 28, 2011 7:20 PM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] CMake, tomorrow (Sunday 23rd)
Re: In Windows (XP WIN32
On Tue, 2011-10-25 at 18:47 +0100, James Turner wrote:
On 25 Oct 2011, at 15:20, Geoff McLane wrote:
need to see the arguments / environment
passed to CMake, to understand why.
But in each case I have explicitly given you
the exact exports and cmake commands used...
What
On Monday, October 24, 2011 16:53:23 James Turner wrote:
Mathias' suggestion also works, BTW - specify CMAKE_PREFIX_PATH, with one
(or several) paths to search - I tested that this morning and updated the
README.
As you guessed, manually setting the the detection variables
On 25 Oct 2011, at 09:39, Adrian Musceac wrote:
Hi James, and thanks for updating the readme. I may be blind or just stupid,
but I can't find a way of setting CMAKE_PREFIX_PATH in KDevelop that works.
Adding it to environment variables does not do anything, and cmake fails to
find the
On Mon, 2011-10-24 at 14:53 +0100, James Turner wrote:
On 24 Oct 2011, at 13:17, Geoff McLane wrote:
In my case I like to be able to compile
against different versions of say OSG - like -
OSG301=1# stable release 3.0.1 - default
OSG283=0# general release 283 -
On 25 Oct 2011, at 15:20, Geoff McLane wrote:
need to see the arguments / environment
passed to CMake, to understand why.
But in each case I have explicitly given you
the exact exports and cmake commands used...
What more do you need?
The problem is you've confused me, with all the
developers discussions
Subject: Re: [Flightgear-devel] CMake, tomorrow (Sunday 23rd)
Hi All,
HELP needed ;=((
Trying to compile the latest FG git, updated just hours
ago, in Ubuntu 10.04, using CMake...
---snip
CMake Error
at /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:70
Hi James,
Thanks for your reply, and from Mathius and
Alan...
Does that help at all?
Well, there is no doubt I could 'simplify' the
situation by NOT appending an extra path items
after 'install', but I should not have to!
If I wanted such a 'simple' single install path,
why not install
On 24 Oct 2011, at 13:17, Geoff McLane wrote:
In my case I like to be able to compile
against different versions of say OSG - like -
OSG301=1# stable release 3.0.1 - default
OSG283=0# general release 283 - option
OSG299=0# another development release
OSGTRUNK=0
-Original Message-
From: James Turner
Sent: Monday, October 24, 2011 2:53 PM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] CMake, tomorrow (Sunday 23rd)
As you guessed, manually setting the the detection variables
(SIMGEAR_VERSION_OK, etc) is a bad idea, unless
On Sat, 2011-10-22 at 16:03 +0100, James Turner wrote:
If there's lingering queries about Cmake, or requests on the 'best' way to
handle the transition, please let me know. Feedback on the README file would
be appreciated too, or even commits / patches to improve it!
CMake worked like a
On 23 Oct 2011, at 09:31, Erik Hofman wrote:
CMake worked like a charm but I did notice that the special purpose
FDM's don't get included anymore. I believe I did see it mentioned in
the CMake configuration but leaving code out on a development system
might introduce a chance of bit-rot.
On Sun, 2011-10-23 at 09:44 +0100, James Turner wrote:
The special purpose FDMs are disabled by default, it's one line to make them
enabled by default of course!
Actually, one of my post CMake build plans, is to make all the FDMs
switchable at build-time, partly because I'm sick of all the
Hi All,
HELP needed ;=((
Trying to compile the latest FG git, updated just hours
ago, in Ubuntu 10.04, using CMake...
First tried -
.../source$ export OSG_DIR=/home/geoff/fg/fg16/install/OSG301
.../source$ cmake -D CMAKE_BUILD_TYPE=Release -D CMAKE_CXX_FLAGS=-O3 \
-D LIB_POSTFIX= \
-D
Hi,
On Sunday, October 23, 2011 21:44:53 James Turner wrote:
I'm not sure *exactly* what you're doing wrong, but in general I would say
you're over controlling things a little.
I'm not clear why you are installing each component in a subdir of install
- that's making your life complicated.
On Sat, Oct 22, 2011 at 10:03 AM, James Turner wrote:
Hello again,
Barring last-minute objections, I would like to declare CMake 'the' build
system, from tomorrow onwards. Since my last email I've added a README.cmake
to flightgear, and I'm working on ensuring the 'make dist' features of
-Original Message-
From: James Turner
Sent: Saturday, October 22, 2011 4:03 PM
To: FlightGear developers discussions
Subject: [Flightgear-devel] CMake, tomorrow (Sunday 23rd)
If there's lingering queries about Cmake, or requests on the 'best' way to
handle the transition, please let
On 22 Oct 2011, at 16:09, Curtis Olson wrote:
It might be a bit extra work, but it would be good to take the source.tar.gz
files that cmake creates, unpack them in a new directory and just make sure
we can do a clean build from them. This always seems to expose a file or
two, or a header
Hi,
On Tuesday, October 18, 2011 10:40:41 James Turner wrote:
I've written this up, at least a first attempt, will commit it later today,
and people can review it for sanity / correctness / omissions :)
Great thanks!
Mathias
to SIMGEAR_VERSION_OK, Type to BOOL
and tick the Value box.
Press OK and continue.
This bypasses the broken Simgear version check.
Alan
-Original Message-
From: Rob Dosogne
Sent: Tuesday, October 18, 2011 10:06 PM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel
On 17 Oct 2011, at 18:38, Curtis Olson wrote:
Would it be possible to write a quick howto for doing some basic
coding/developer things in cmake. Like: how to add a new source file to the
project. Or how to add a new module/library to the project.Maybe a
few quick summeries of how to
have left something out, but this does describe the basic process.
Alan
From: James Turner
Sent: Tuesday, October 18, 2011 9:40 AM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Cmake (soon)
_
On 17 Oct 2011, at 18:38, Curtis Olson wrote:
Would it be possible to write
. Flightgear and other executables should be in C:\Flightgear\install\bin.
No doubt I have left something out, but this does describe the basic
process.
Alan
From: James Turner
Sent: Tuesday, October 18, 2011 9:40 AM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Cmake (soon
Hi James,
Thanks. I was off line all day test flying our UAS so it looks like I have
some serious catch up to do here on several fronts. :-)
Curt.
On Tue, Oct 18, 2011 at 3:40 AM, James Turner zakal...@mac.com wrote:
On 17 Oct 2011, at 18:38, Curtis Olson wrote:
Would it be possible to
Hi James,
One thing that stresses me out is large scale technology changes with no
documentation or howto's to back them up. This change might be fine for
people who are cmake experts. And I know anyone can start from scratch and
read the cmake manual from cover to cover. But that takes time
Am 17.10.2011 19:10, schrieb James Turner:
It's been a month since I announced the intention, to switch all the main FG
platforms to use CMake, and to deprecate and remove the other build systems
from Git. There's been many small improvements in the Cmake files since then,
which I hope
Hi
On 11 Sep 2011, at 20:25, Bertrand Coconnier wrote:
Have you tried to append your flag with :STRING ? It should look
like -D CMAKE_CXX_FLAGS:STRING=-O3 -Wall -march=native.
I finally had the time to try this out. Works like a charm. :-)
Cheers,
Durk
I'm uninstall OSG-3.0.1, SG-git and FG-git.
Then make fresh folder for each of them, succesfully compile OSG and SG with
~[OSG/SG]/build$ ccmake ..
configure,
generate,
~[OSG/SG]/build$ make install
but FG, with same commands, fails: http://pastebin.com/2V0AL0nY
--
---
WBR, Vadym.
Le 12/09/2011 21:31, Stuart Buchanan a écrit :
2011/9/12 Mathias Fröhlich :
On Sunday, September 11, 2011 21:29:28 Durk Talsma wrote:
My error was in SimGear, and your fix was for FlightGear, it I'm correct.
So, I'm not sure if that would fix it.
Hmm, then probably not...
... but I have done
On Sat, Sep 17, 2011 at 6:29 PM, Citronnier - Alexis Bory wrote:
Hi,
Unfortunately I'm stuck at the same point with no idea on how to solve
this one. Here the error with my own paths:
snip
CMake Error at
/usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:70
(MESSAGE):
Hi,
I am a bit away from that stuff currently. Currently checking mail in vacation
...
But:
On Saturday, September 17, 2011 19:29:14 Citronnier - Alexis Bory wrote:
alexis@duck:~/fgfs/install/build-flightgear$ cmake -D
CMAKE_INSTALL_PREFIX:PATH=/home/alexis/fgfs/install/fgfs -D
Hi Durk,
On Sunday, September 11, 2011 21:29:28 Durk Talsma wrote:
My error was in SimGear, and your fix was for FlightGear, it I'm correct.
So, I'm not sure if that would fix it.
Hmm, then probably not...
... but I have done the same change in the identical file in simgear now.
I did not know
Subject: Re: [Flightgear-devel] Cmake
Hi Durk,
On Sunday, September 11, 2011 21:29:28 Durk Talsma wrote:
My error was in SimGear, and your fix was for FlightGear, it I'm correct.
So, I'm not sure if that would fix it.
Hmm, then probably not...
... but I have done the same change
2011/9/12 Mathias Fröhlich :
On Sunday, September 11, 2011 21:29:28 Durk Talsma wrote:
My error was in SimGear, and your fix was for FlightGear, it I'm correct.
So, I'm not sure if that would fix it.
Hmm, then probably not...
... but I have done the same change in the identical file in
Hi Mathias,
On 10 Sep 2011, at 10:57, Mathias Fröhlich wrote:
Hi,
Ok, then it's probably best to deinstall the distros cmake and install cmake
from sources. Or may be cmake has some binary distributions that fits your
needs.
Thanks for your suggestion (and to Fred as well). All
Hello,
Am 11.09.2011 09:57, schrieb Durk Talsma:
[..] I hope that FlightGear will behave nicely with the
xinerama xserver configuration, because I'm running kde4, which
apparently doesn't like multiple monitor configurations that much
I'm using a double monitor setup here with 11.4/KDE4
Christian Schmitt wrote:
I have used CMake in the Gentoo packages pretty much from the start, but
right now I'm experiencing some problems: all is good as long as I have
libsvn support enabled in SG and FG. When I disable it in SG and want to
recompile FG afterwards (also disabled, of
Hi,
On Sunday, September 11, 2011 12:55:33 Christian Schmitt wrote:
This is now solved with the latest FG git version. Thanks!
Ok, thanks, I was on the way asking for that :)
Mathias
--
Using storage to extend the
Hi Andreas,
On 11 Sep 2011, at 12:18, Andreas Gaeb wrote:
one problem I noticed with that is that the headers aren't added to the
project in SimGear. At least Codeblocks is not able to add them automatically
parsing the includes, so the attached patch does that explicitly. This allows
2011/9/11 Durk Talsma durkt...@gmail.com:
Which actually brings me to the next question: I'm currently trying to build
a heavily optimized version of FlightGear, and want to pass a number of
options cmake. I got the basic mechanism to work; i.e. -D
CMAKE_CXX_FLAGS=-O3 -Wall. But, in my
On 11 Sep 2011, at 20:25, Bertrand Coconnier wrote:
Have you tried to append your flag with :STRING ? It should look
like -D CMAKE_CXX_FLAGS:STRING=-O3 -Wall -march=native.
Not yet, but I'll certainly give it a try.
Thanks!
Cheers,
Durk
On 11 Sep 2011, at 13:18, Mathias Fröhlich wrote:
Hi,
On Sunday, September 11, 2011 12:15:42 Durk Talsma wrote:
-- Configuring incomplete, errors occurred!
I don't get that hard error, but I have checked in something that fixes
similar
symptoms. So, could you retry?
Hi Mathias,
My
On Monday 05 September 2011 10:10:27 Curtis Olson wrote:
Are there any cmake based build instructions available anywhere? I'm not
seeing them.
I'm just hoping the cmake jocks will put themselves in the position of
non-cmake jocks and help ease the transition from multiple fronts for many
If you regularly pull+build 'next', please try a cmake based build, and
report any issues you encounter - CMake should work 'out of the box' on Mac
(Makefiles or XCode), Linux (32- and 64- bit) and Windows (VisualStudio 2008
and 2010 - mingw and cygwin may need some fixes).
Hi James,
Hi Durk,
- Mail original -
If you regularly pull+build 'next', please try a cmake based build,
and report any issues you encounter - CMake should work 'out of
the box' on Mac (Makefiles or XCode), Linux (32- and 64- bit) and
Windows (VisualStudio 2008 and 2010 - mingw and
hi Fred,
On 10 Sep 2011, at 10:28, Frederic Bouvier wrote:
Hi Durk,
FindOpenSceneGraph.cmake is in the Cmake distribution, in the share
directory. You certainly need to tell Cmake where the installed OSG is.
Regards,
-Fred
Thanks; looking at /usr/share/cmake/Modules, I see that I
- Mail original -
hi Fred,
On 10 Sep 2011, at 10:28, Frederic Bouvier wrote:
Hi Durk,
FindOpenSceneGraph.cmake is in the Cmake distribution, in the share
directory. You certainly need to tell Cmake where the installed
OSG is.
Regards,
-Fred
Thanks; looking
Hi Durk,
On Saturday, September 10, 2011 10:28:22 Frederic Bouvier wrote:
FindOpenSceneGraph.cmake is in the Cmake distribution, in the share
directory. You certainly need to tell Cmake where the installed OSG is.
Correct, this should be cmake provided.
So, cmake does not find its own files.
Hi,
On Saturday, September 10, 2011 10:46:03 Durk Talsma wrote:
Thanks; looking at /usr/share/cmake/Modules, I see that I have a
Findosg.cmake file, as well as several Findosg*.cmake files, but no
FindOpenSceneGraph.cmake. FWIW, this is one an opensuse 10.0, running
cmake version 2.6 - patch
James Turner wrote:
If you regularly pull+build 'next', please try a cmake based build, and
report any issues you encounter - CMake should work 'out of the box' on
Mac (Makefiles or XCode), Linux (32- and 64- bit) and Windows
(VisualStudio 2008 and 2010 - mingw and cygwin may need some
Please don´t.
I reverted from VC100 to VC90 as the Cmake process was always failing.
There is a difference between Hudson saying that all is OK with Cmake and
Visual Studio VC100 producing working executables.
This was all with the de-facto standard 3rd party package from
Hi,
On Monday, September 05, 2011 14:47:44 Alan Teeder wrote:
Please don´t.
I reverted from VC100 to VC90 as the Cmake process was always failing.
There is a difference between Hudson saying that all is OK with Cmake and
Visual Studio VC100 producing working executables.
This was all
So I have nothing against cmake, it sounds like it offers some nice
features. But I assume those that want to push this change forward, will
take some time to write up some basic howto's so that people who have never
used it as a developer can get up to speed without too many problems?
Right now
Curtis Olson wrote:
I'm just hoping the cmake jocks will put themselves in the position of
non-cmake jocks and help ease the transition from multiple fronts for many
of our different classes of users/developers.
With CMake there's a list of flags you're appending to the 'cmake' call
similarly
Is there support for the --prefix= concept of autoconf? I really struggled
to find anything like that in OSG's cmake config and it appeared I would be
forced to define a really ugly/long list of environment variables before
running make install in order to accomplish a similar thing (installing
Is this an option to cmake at the configure step, or to make at the
build/install step? Can this work as an environment variable? What if I
want to pick up build libraries from a non-standard location ... maybe I'd
like to install a particular version of FG and a particular version of all
it's
-Original Message-
From: MathiasFröhlich
Sent: Monday, September 05, 2011 4:28 PM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Cmake
Hi,
On Monday, September 05, 2011 14:47:44 Alan Teeder wrote:
Please don´t.
I reverted from VC100 to VC90 as the Cmake
Curtis Olson wrote:
Is this an option to cmake at the configure step, or to make at the
build/install step?
The install prefix is set at the configure step - CMake is quite
similar to Autoconf in this respect. To put an example, configuring
SimGear on a setup with TerraSync/SVN explicitly
On 5 Sep 2011, at 17:10, Curtis Olson wrote:
So I have nothing against cmake, it sounds like it offers some nice features.
But I assume those that want to push this change forward, will take some
time to write up some basic howto's so that people who have never used it as
a developer can
Allan
I know nothing about building on windows, but I have found installing osg
multiple times on linux can cause issues as it does not always un-install
cleanly, and the next install may not overwrite what is left behind. All is
nice till you try and compile against it. Especially if its a
Hi Allan,
this issue has been discussed on the osg ML and is likely a bug in VS2010.
These warnings are the best we can do. By default, these are errors, but the
cmake configure script adds /FORCE:MULTIPLE to allow multiply defined symbols
in an executable.
Regards,
-Fred
- Alan Teeder
1 - 100 of 118 matches
Mail list logo
