Flightgear 1.9.1 - Kfreeflight - Testers needed

[hoos]

Martin,

I couldn't withstand the urge to take a further look into Atlas.

'Configure' went like this:

----> last couple of lines
checking plib/pu.h usability... yes
checking plib/pu.h presence... yes
checking for plib/pu.h... yes
checking for ulInit in -lplibul... no
checking simgear/version.h usability... no
checking simgear/version.h presence... no
checking for simgear/version.h... no

You *must* have the SimGear support library installed on your system
to build the FGFS simulator!

Please see README.SimGear for more details.

configure aborted.


As you see there's an issue regarding simgear,
apparently some path cannot be found.


BTW I tried different configure prefixes (=paths).

   ch, H.  

[MBantz]

Hoos! Way to cool!

I have the library handy right here :-) took me a day to compile and get the dependencies right :-) Didn't upload it because it is only for development.

Would you like to try and install a build environment and build Atlas? (and become a builder ;-) This would be the perfect way to get Atlas running and I'll gladly help you out :-) And a fine project to begin with.

I have to hurry to get the Simgear library uploaded, my daughter just let me have my laptop for 2 mins. :-) The library RPM is uploaded in a short while,

cheers

[hoos]

Martin!,

I'll keep in mind if I want to set up a testing environment.

Anyway, as far as I can see the -devel's are not complete yet, have a look:

[root@localhost FG-devel]# apt-get install *.rpm
Reading Package Lists... Done
Building Dependency Tree... Done
Selecting libOpenSceneGraph-devel for 'libOpenSceneGraph-devel-2.8.1-1pclos2009.i586.rpm'
Selecting libOpenThreads-devel for 'libOpenThreads-devel-2.8.1-1pclos2009.i586.rpm'
Selecting openal-soft-devel for 'openal-soft-devel-1.8.466-1pclos2009.i586.rpm'
Selecting SimGear-devel for 'SimGear-devel-1.9.1-1pclos2009.i586.rpm'
Some packages could not be installed. This may mean that you have
requested an impossible situation or that some of the repositories
in use are in an inconsistent state at the moment.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  SimGear-devel: Depends: plib-devel
  openal-soft-devel: Depends: openal-soft (= 1.8.466) but it is not installable
                     Conflicts: openal-devel (<= 0.0.8 )
E: Broken packages
[root@localhost FG-devel]#

Hidtil   ;

          Skol, Hoos.

[MBantz]

Ups! Sorry for that,

when I get my laptop back from my daughter I'll upload the missing dependencies,

cheers

[MBantz]

Ah, now I see whats going on (just got my laptop back ;-) Delete the openal-soft-devel (and openal-soft if there is one) I dropped this library but uploaded it by mistake - instead download the libplib and libplib-devel, then you should be fine.

What's your status on FlightGear and Kfreeflight? For now I almost would prefer just to upload FlightGear (and Atlas perhaps) and wait for the new Kfreeflight - pleas let me know your thoughts,

cheers
Martin

[hoos]

Martin!

Version issue here whwn configuring Atlas,
have a look:

--------> last couple of lines:
checking how to run the C++ preprocessor... g++ -E
checking plib/pu.h usability... yes
checking plib/pu.h presence... yes
checking for plib/pu.h... yes
checking for ulInit in -lplibul... yes
checking simgear/version.h usability... yes
checking simgear/version.h presence... yes
checking for simgear/version.h... yes
checking for proper simgear version... wrong version
configure: error: Install latest simgear first...

Any idea?   

           Cheers, Hoos.

[MBantz]

i'm looking at Atlas also, and it is not the easiest program to handle! Darn.

I grabbed the CVS version, this includes autogen.sh that I assume is finding the simgear version - because this error is not with the CVS version.

Next thing you run into, is jpeglib.h - you will probably get a 'bad reference' when compiling, and it appears the jpeglib.h need to be patched to allow a c++ program to compile this c code. I have done this and after that it compiles fine. I will grab the libjpeg and put this patch in later (before sending to contribs).

I'm at the installation part now and both Map and Atlas throws strange errors at me.... fighting them off one-by-one with a large cup of coffee right now.

Let me know if you will have the patch to jpeglib.h (I'm little worried to give it if you don't compile in a VM). If you like I can send references on how to use VMWare to build as I do,

cheers

[MBantz]

OK, did some digging,

the Atlas developers are still working on version 0.4.0 and users have issues with both the tarball 0.3.0 and the CVS version 0.4.0. I can run Atlas (0.4.0), but not the associated Map application (that generate the maps). I've sent a mail to the developers for helping out with testing - and I prefer to wait for the official release of 0.4.0.

Kfreeflight is able to construct parameters to FlightGear that stalls the program. It is built for FlightGear 1.0 and much have changed. Most, but not all of Kfreeflight works with FlightGear 1.9.1 - so I will not include it, but wait for the soon-to-come Kfreeflight KDE4 version (and of course PCLinux KDE4). Then we can package Kfreeflight and Atlas in versions that are updated and written for FlightGear 1.9.1.

I will soon send FlightGear 1.9.1. to contribs,

cheers
MBantz

[hoos]

Martin!

Thanks very much!
I'll leave Kfreeflight for what it is at the moment.
As far as I can see FG is ready for use to everyone indeed.
As far as package building goes I might use Virtual Box
which already works here (I run a nice stripped down version of XP
for photographic purposes).
But I'm not a qualified builder yet although I've compiled a lot,
including kernels, but just for home use :-)

        again thanks, cheers, Hoos.

[MBantz]

I was not quit satisfied with the flighgear directories and the wrapperscripts, so I have cleaned the installation and removed the wrapperscripts.

I have added the graphical frontend fgrun that can be launched from the menu (games/other). This program is not so full-featured as Kfreeflight, but newer, and I will look at Kfreeflight and Atlas when they are updated for Flightgear 1.9.1.

Fgrun handles Terrasync, you just need to set the directory to the terrasync folder. As before, you need to let Terrasync download airport information and other stuff when changing airport. Fgrun has a nice logwindow where scenery downloads can be monitored. I chose to use the user home directory (.fsfg directory) to put terrasync download, due to security and that each user probably uses the same airports when flying.

Grab the 9 rpm's - the link is in the first post in this thread,

cheers