Re: [Flightgear-devel] Terragear now sans plib
Christian Schmitt wrote: [...] These changes are not yet in the master tree, but can be tested in the topics/cmake-integration branch. Please do so, if possible, so we can iron out any showstoppers. Apparently directory path handling has been changed recently in a way which prevents 'terrafit' from recursively walking the given directory tree. This issue is with cmake-integration/CMake, cmake-integration/Autoconf but master/Autoconf is fine. I'm also observing a similar behaviour at 'raw2ascii' with cmake-integration/CMake (didn't test Autoconf). All these test had been performed with recent Gitorious 'simgear'. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Terragear now sans plib
On 26 Oct 2011, at 13:13, Martin Spott wrote: Apparently directory path handling has been changed recently in a way which prevents 'terrafit' from recursively walking the given directory tree. This issue is with cmake-integration/CMake, cmake-integration/Autoconf but master/Autoconf is fine. I'm also observing a similar behaviour at 'raw2ascii' with cmake-integration/CMake (didn't test Autoconf). This is certainly my fault, as part of the changes to switch to using the simgear path/directory handling, instead of PLIB. Can you describe / give me a minimal test setup? My inability to easily test such changes is the main reason I don't want to merge to master yet :) I've been relying on Chris to test some pieces, but there's a lot of different tools in TerraGear. James -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Terragear now sans plib
Martin Spott wrote: Apparently directory path handling has been changed recently in a way which prevents 'terrafit' from recursively walking the given directory tree. This issue is with cmake-integration/CMake, cmake-integration/Autoconf but master/Autoconf is fine. I'm also observing a similar behaviour at 'raw2ascii' with cmake-integration/CMake (didn't test Autoconf). I was interrupted when writing the above As an addition I'd propose to separate the de-PLIB-ifying from the 'cmake-integration' into a separate branch/topic/whatever because the move to CMake as a build system appears to be successful. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Terragear now sans plib
On 26 Oct 2011, at 13:34, Martin Spott wrote: I was interrupted when writing the above As an addition I'd propose to separate the de-PLIB-ifying from the 'cmake-integration' into a separate branch/topic/whatever because the move to CMake as a build system appears to be successful. A fair suggestion! I originally combined them because it was easier not to worry about PLIB when creating the CMake files, but I wasn't expecting the slightly-complex changes to de-PLIB the file handling code. Let me see how hard it would be, to un-pick the changes. James -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Terragear now sans plib
On Wed, 2011-10-26 at 13:19 +0100, James Turner wrote: On 26 Oct 2011, at 13:13, Martin Spott wrote: Apparently directory path handling has been changed recently in a way which prevents 'terrafit' from recursively walking the given directory tree. This issue is with cmake-integration/CMake, cmake-integration/Autoconf but master/Autoconf is fine. I'm also observing a similar behaviour at 'raw2ascii' with cmake-integration/CMake (didn't test Autoconf). This is certainly my fault, as part of the changes to switch to using the simgear path/directory handling, instead of PLIB. Can you describe / give me a minimal test setup? My inability to easily test such changes is the main reason I don't want to merge to master yet :) I've been relying on Chris to test some pieces, but there's a lot of different tools in TerraGear. James Hi James, Martin, From a git pull Oct 24 I too could NOT get master 'raw2ascii' to compile using automake ;=(( An error something like - 'do not know how to make main.c from main.o' which I did NOT understand... seems reversed! And why 'main.c', since the Makefile.am shows only - raw2ascii_SOURCES = main.cxx rawdem.c rawdem.h There is no main.c here??? No particular setup... just the usual ./autogen.sh; ./configure [options, including with-simgear=, with-plib= etc]; and make, that has worked before... Except of course this is against sg-git, and osg-301. In my case the FULL command was - tmp/templog55.txt:Doing TG ./configure \ --prefix=/home/geoff --exec-prefix=/home/geoff \ --with-osg=/home/geoff/fg/fg16/install/OSG301 \ --with-simgear=/home/geoff/fg/fg16/install/simgear \ --with-plib=/usr --disable-ogrdecode \ --disable-poly2ogr Have not tried the cmake branch yet, but hope to get around to it soon... Need a heads up about the removal of PLIB dependence eventually in master, since I will need to adjust my makefg script, which also makes TG, to match, but all this is now arriving nicely as part of the commitlogs - Thanks... Regards, Geoff. -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Terragear now sans plib
James Turner wrote:
Can you describe / give me a minimal test setup?
Difficult, because 'hgtchop' doesn't work any more either, not even
with terragear-cs/master ;-)
Try this one for the preparational step - adapt from my setup:
DATADIR=${HOME}/archive/GIS/GISData/SRTM/version2_1/HGT/SRTM3
WORKDIR=${HOME}/workdir
mkdir -p ${WORKDIR}
for REGION in Islands; do
for HGTFLE in ${DATADIR}/${REGION}/*.hgt.zip; do
hgtchop 3 ${HGTFLE} ${WORKDIR}/SRTM2-${REGION}-3
done
done
At the current state this leaves an empty ~/workdir/ whereas the
directory should contain approx. 1k files in 170 subdirectories.
The respective SRTM files are available here - unless you prefer to use
the 'authoritative' source:
ftp://ftp.ihg.uni-duisburg.de/GIS/GISData/SRTM/version2_1/HGT/SRTM3/Islands/
Cheers,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--
--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Terragear now sans plib
Geoff McLane wrote: An error something like - 'do not know how to make main.c from main.o' which I did NOT understand... seems reversed! And why 'main.c', since the Makefile.am shows only - raw2ascii_SOURCES = main.cxx rawdem.c rawdem.h There is no main.c here??? Hi, this is caused by old .dep dirs and files lying around, which still contain the old names (main was renamed recently). So either restart with a fresh repo checkout, or do a grep for main.c in src/Prep/DemRaw2ascii and change it accordingly. HTH Chris -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Terragear now sans plib
James Turner wrote: A fair suggestion! I originally combined them because it was easier not to worry about PLIB when creating the CMake files, but I wasn't expecting the slightly-complex changes to de-PLIB the file handling code. Let me see how hard it would be, to un-pick the changes. I'm pretty good at untangling git commits, but IMHO, let's only do that if it is clear that the current directory problems can't be rectified with 1-2 more commits. Seperating cmake from de-plib might be far more work. Chris -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Terragear now sans plib
On Wed, 2011-10-26 at 15:38 +0200, Christian Schmitt wrote: Geoff McLane wrote: An error something like - 'do not know how to make main.c from main.o' which I did NOT understand... seems reversed! And why 'main.c', since the Makefile.am shows only - raw2ascii_SOURCES = main.cxx rawdem.c rawdem.h There is no main.c here??? Hi, this is caused by old .dep dirs and files lying around, which still contain the old names (main was renamed recently). So either restart with a fresh repo checkout, or do a grep for main.c in src/Prep/DemRaw2ascii and change it accordingly. HTH Chris Hi Chris, Wow, it helped immensely ;=)) Renamed terragear-cs to tg-cs-old, and did a fresh clone, configure, compile, install, ... and 3 min 24 secs later was all done perfectly... Went back and looked in tg-cs-old/src/Prep/DemRaw2ascii, and sure enough .deps/main.Po contained main.o: main.c ../../../src/Include/config.h /usr/include/stdio.h \ Tar muchly... will watch for that in future ;=)) Regards, Geoff. -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Terragear now sans plib
James Turner wrote: Can you describe / give me a minimal test setup? I'm really running out of ideas and my buget of testing time for today (maybe this week) is exhausted. I've tested various pairings of 'simgear' and 'terragear-cs', unfortunately without getting a 'hgtchop' creating subdirectories and/or files. Anyhow I'd like to hear from others being more successful with using recent versions of the 'terragear-cs' tools. For now, in order to build terrain, I'd recomment simgear-cs at 6284fc22d56d3ca5b447c232e22369d3f0a23d0e and terragear-cs at 1707ec7fbfe09eb39951539334573aa6b1762804 Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] CMake, tomorrow (Sunday 23rd)
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 more do you need?
The problem is you've confused me, with all the discussion :) So it would
help, to be able to see exactly the commands, all of them, in one place -
maybe upload your scripts to someplace? Then I can get an overview of what
you're doing.
Hi James,
This problem was happening in BOTH Ubuntu linux,
and in XP WIN32...
BUT at least in Ubuntu, I think some of the problem
was that I was NOT deleting the CMakeCache.txt file
each time I modified the script for another try...
Remember the abort I was getting was :-
Could NOT find SimGear (missing: SIMGEAR_VERSION_OK)
Now I seem to have found a combination that works -
(a) Setting the environment -
makefg: Done export SIMGEAR_DIR=/media/Disk2/FG/fg17/install/simgear
AND
(b) adding SIMGEAR_INCLUDE_DIR
makefg: Will do 'cmake -D CMAKE_BUILD_TYPE=Release \
-D CMAKE_CXX_FLAGS=-O3 -D LIB_POSTFIX= \
-D CMAKE_INSTALL_PREFIX:PATH=/media/Disk2/FG/fg17/install/fgfs \
-D ENABLE_RTI=OFF -D CMAKE_VERBOSE_MAKEFILE=TRUE \
-D SIMGEAR_LIBRARIES=/media/Disk2/FG/fg17/install/simgear/lib \
-D SIMGEAR_INCLUDE_DIR=/media/Disk2/FG/fg17/install/simgear/include\
.'
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 reached another wall...
fgjs will not link ;=((
Linking CXX executable fgjs
cd /media/Disk2/FG/fg17/fgfs/source/src/Input /usr/bin/cmake -E
cmake_link_script CMakeFiles/fgjs.dir/link.txt --verbose=1
/usr/bin/c++ -O3 -Wall -D_REENTRANT -O3 -DNDEBUG
CMakeFiles/fgjs.dir/fgjs.cxx.o CMakeFiles/fgjs.dir/jsinput.cxx.o
CMakeFiles/fgjs.dir/jssuper.cxx.o -o fgjs -rdynamic -Wl,-Bstatic
-lplibpuaux -lplibjs -lplibfnt -lplibssg -lplibsg -lplibpu -lplibul
-Wl,-Bdynamic
CMakeFiles/fgjs.dir/fgjs.cxx.o: In function
`fgScanForOption(std::basic_stringchar, std::char_traitschar,
std::allocatorchar const, std::basic_stringchar,
std::char_traitschar, std::allocatorchar const)':
fgjs.cxx:(.text+0x12b): undefined reference to
`sg_gzifstream::sg_gzifstream(std::basic_stringchar,
std::char_traitschar, std::allocatorchar const,
std::_Ios_Openmode)'
fgjs.cxx:(.text+0x13c): undefined reference to
`logstream::initGlobalLogstream()'
fgjs.cxx:(.text+0x142): undefined reference to `logbuf::logClass'
fgjs.cxx:(.text+0x15f): undefined reference to
`skipcomment(std::basic_istreamchar, std::char_traitschar )'
fgjs.cxx:(.text+0x21f): undefined reference to
`skipcomment(std::basic_istreamchar, std::char_traitschar )'
fgjs.cxx:(.text+0x295): undefined reference to `gzfilebuf::~gzfilebuf()'
fgjs.cxx:(.text+0x2ca): undefined reference to `logbuf::logPriority'
[snip]
This is missing SG gzip and logbuf, and can NOT see
ANY SG libraries in the link, like -lsgdebug,
etc...very puzzling???
Maybe this is related to EVENT_INPUT which
defaults ON for APPLE, but has a comment
for linux -
elseif(CMAKE_SYSTEM_NAME MATCHES Linux)
# disabled while DBus / HAL / udev issues are decided
#set(EVENT_INPUT_DEFAULT 1)
and later
option(EVENT_INPUT
Set to ON to build FlightGear with event-based Input support
${EVENT_INPUT_DEFAULT})
but maybe this has nothing to do with it...
Anyway, out of time for exploration tonight,
but look forward to any suggestions for
continuing tomorrow...
As mentioned I am trying to update my script to
use CMake... The previous versions of the script are
published here -
http://geoffair.org/fg/fgfs-052.htm
BUT because this 'cmake' version 1.3.5 is
not yet fully tested, and sometimes failing,
I have not yet published it on that page, but a
copy of it is here for testing :-
http://geoffair.org/tmp/makefg
Regards,
Geoff.
--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Terragear now sans plib
On 26 Oct 2011, at 18:43, Martin Spott wrote: I've tested various pairings of 'simgear' and 'terragear-cs', unfortunately without getting a 'hgtchop' creating subdirectories and/or files. Anyhow I'd like to hear from others being more successful with using recent versions of the 'terragear-cs' tools. Just pushed a fix (to SimGear) - I changed the behaviour of an SGPath method, a few weeks ago, thinking no one would be relying on the 'old' behaviour ... turns out several places in TerraGear rely on exactly the behaviour I thought was crazy :) I've pushed a fix to Simgear, updated the tests, and now I can run hgtchop happily with latest simgear and terragear. James -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgdata: Important note
On Tue, Oct 25, 2011 at 7:33 PM, HB-GRAL flightg...@sablonier.ch wrote: Am 25.10.11 18:54, schrieb Gijs de Rooy: No matter what aircraft-split we end up with, aircraft authors will always be able to update their own aircraft at any time. Hope so ;-) With the current setup you can for example commit (and accept merge requests) for your EC130:https://gitorious.org/flightgear-aircraft/ec130 But I want to give commit rights to my wife to my repo, without asking you, can I do that ? Why not ? What gives the team the right to decide if my wife could be contributor in my aircraft project or not ?! When you start on a new aircraft and would like to have its repository under the FlightGear Aircraft project, you do have to ask one of the people from the team: https://gitorious.org/+flightgear-aircraft For every single aircraft ? Hm, everyone ? You also have to contact that teammembers when you'd like to get access to an existing repo (or give someone else access to your aircraft's repo). Sorry, Peter is not here since six months, but Paul - ok, he does not know a lot about your project - but he will give access to Alex, to update Sabins repo permissions. The #1 reason I haven't added my projects (MD-81, Grumman Goose, Edgley Optica, Velocity XL RG) to the repository is that I have no ability to perform my own commits. Possibly I haven't earned the right and I can understand that. But I would like to learn and understand the procedure for how one earns these rights, and maybe others would too. Don't get me wrong-- for core FG work I readily see the value in maintaining a short-list of those with commit rights and/or peer-review before commits. But for non-core work such as aircraft projects, it's somewhat bothersome. In the past Durk has been kind enough to submit my 1049H Constellation to the repository. I'm grateful and I am certain he would readily continue to do so. But I dislike troubling him (or anyone else) to do it. Durk and others do great work here and I don't like adding busy-work to their plate. -Gary aka Buckaroo -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
