Hi, Csaba
Yes against OSG 2.9.10, i did built simgear flightgear from cleaned source
( copied from Git)
Which mean:
autogen.sh configure make sudo make install .
don't bother , thanks for the answer.
i will wait for a better stable version osg compatible.
2011/2/6 Csaba Halász
> On Sun,
On Sun, Feb 6, 2011 at 12:45 AM, henri orange wrote:
> Hi,
>
> built OSG 2.9.10 again , and built Simgear Flightgear again gives the same
> error.
>
> Then, since OSG 2.9.11, is available.
> I have just built osg 2.9.11,
> Unfortunately simgear built against it, gives the following error
> What i
Hi,
built OSG 2.9.10 again , and built Simgear Flightgear again gives the same
error.
Then, since OSG 2.9.11, is available.
I have just built osg 2.9.11,
Unfortunately simgear built against it, gives the following error
mv -f .deps/CheckSceneryVisitor.Tpo .deps/CheckSceneryVisitor.Po
g++ -DHAVE
As many of you might be aware of, a group of FlightGear enthusiasts have been
presenting FlightGear at FSWeekend in Lelystad(NL) and LinuxTag in Berlin(DE)
over the last years. Our presentation and the equipment list has grown with
each show with every single item being donated by the beforement
Here locally I made a local clone of the fgdata repository using "git clone
-l fgdata fgdata-wip". That seemed to work as advertised.
I noticed that the only branch available in the new local clone "fgdata-wip"
is the branch that is active in fgdata at the time the clone is made
that's good
On 05.02.2011 18:54, henri orange wrote:
> ,
>
> I get an error at build
>
> screen-dump.cxx:(.text+0x276): undefined reference to
> `osg::Referenced::signalObserversAndDelete(bool, bool) const'
> /usr/local/lib/libsgmisc.a(PathOptions.o): In function
> `simgear::makeOptionsFromPath(SGPath co
,
I get an error at build
screen-dump.cxx:(.text+0x276): undefined reference to
`osg::Referenced::signalObserversAndDelete(bool, bool) const'
/usr/local/lib/libsgmisc.a(PathOptions.o): In function
`simgear::makeOptionsFromPath(SGPath const&)':
PathOptions.cxx:(.text+0x49): undefined reference
On 05.02.2011 16:21, ThorstenB wrote:
>
> I'm currently testing a different patch for the same issue: instead of
> untieing all properties below the /fdm/jsbsim (only), I added a list
> to JSBSim's FGPropertyManagager, so it keeps track of all the
> properties it has actually bound. It can then
> I'll have to go back and look at the [JSBSim] code again. I'd like to
> figure out how to make resetting work better from the API - more
> "naturally" and without having to reload the aircraft model. This would be
> useful for both the JSBSim standalone executable and for any larger
> simulat
> From: ThorstenB [mailto:bre...@gmail.com]
>
> Hi,
>
> probably spotted the cause for the reported reset crash: it's the same
> as already reported before - targeted by this earlier patch:
> http://www.gitorious.org/fg/flightgear/commit/287cc74965e11ff3888117a9d
> 9b88ed2bdbb9252
>
> This patch
Hi, Thorsten,
May be i can confirm your feeling.
I was looking at the "old" Catalina official gpl version.
It can start at the right mooring place on water, when there is one, close
to the Airport we want to start from ( for instance KSFO, with Mooring place
at Treasure Island, Pan Am base at
ve the conflicts, git add the changed files and continue the
> rebase with
>
> git rebase --continue
>
> (Use of git status is needed here to see which files are in conflict).
>
> As an additional safe-guard you may create a name for your previous
> work before you rebase
Hi,
probably spotted the cause for the reported reset crash: it's the same
as already reported before - targeted by this earlier patch:
http://www.gitorious.org/fg/flightgear/commit/287cc74965e11ff3888117a9d9b88ed2bdbb9252
This patch unties all JSBSim properties prior to reset. However, it's
no
gt;
> (Use of git status is needed here to see which files are in conflict).
>
> As an additional safe-guard you may create a name for your previous work
> before you rebase so that you can easily recover it if t
s needed here to see which files are in conflict).
As an additional safe-guard you may create a name for your previous work
before you rebase so that you can easily recover it if the rebase goes
bad. Assuming your branch is called my-branch the following command
creates a back-up point:
git bra
How can I update my FlightGear development codebase (which was created a
few months ago) from git so I can try to see this problem?
Jon
> -Original Message-
> From: Erik Hofman [mailto:e...@ehofman.com]
> Sent: Saturday, February 05, 2011 6:42 AM
> To: FlightGear developers discussions
>
On Sat, 2011-02-05 at 13:31 +0100, henri orange wrote:
> Hi, Erik
>
> Sorry for the question is there somewhere a specific fg2.2 source ?
>
> I am using the git version with git pull, though i don't understand
> the meaning of it, it does work and give me an update.
> I thought it was the fg deve
Hi, Erik
Sorry for the question is there somewhere a specific fg2.2 source ?
I am using the git version with git pull, though i don't understand the
meaning of it, it does work and give me an update.
I thought it was the fg devel version.
with fgfs --version i get
FlightGear version: 2.2.0
Revi
On Sat, 2011-02-05 at 13:00 +0100, henri orange wrote:
> Hello, devel-members
>
> Again starting the topic ( was oriented to an other direction )
>
> To resume what i was discovering:
> With at least two "official" jsbsim models
>
> 747-400
> p51d
>
> I am getting a segmentation error at reset
Hello, devel-members
Again starting the topic ( was oriented to an other direction )
To resume what i was discovering:
With at least two "official" jsbsim models
747-400
p51d
I am getting a segmentation error at reset.
I don't say these models are wrong, i say there is somewhere, in jsbsim
dur
On Sat, 05 Feb 2011 10:12:33 +0100, Erik wrote in message
<1296897153.1587.1.camel@Raptor>:
> On Sat, 2011-02-05 at 02:25 +0100, Arnt Karlsen wrote:
> > ..relevant to the 747-400 is:
> > failed to load sound buffer:Failed to load wav file: Unsupported
> > mode within an otherwise usable file type
On Sat, 2011-02-05 at 02:25 +0100, Arnt Karlsen wrote:
> ..relevant to the 747-400 is:
> failed to load sound buffer:Failed to load wav file: Unsupported mode
> within an otherwise usable file type
> at
> /home/arnt/FG-git/install/fgfs/bin/../fgdata//Aircraft/747-400/Sounds/FGOS_FlapXtndWClick.wav
22 matches
Mail list logo
