OK, I guess I do crazy things when without knowledge. :)
The time_t error went away when including time.h, but login_tty() is
still undefined.
Looking in the login_tty manual page it says you need to include it with:
#include
So I added that include at the top of fgrun_pty.cxx but it still does
Arthur Wiebe wrote :
if g++ -DHAVE_CONFIG_H -I. -I. -I. -I/FlightGear/include -g -O2 -MT
fgrun_pty.o -MD -MP -MF ".deps/fgrun_pty.Tpo" \
-c -o fgrun_pty.o `test -f 'fgrun_pty.cxx' || echo './'`fgrun_pty.cxx; \
then mv -f ".deps/fgrun_pty.Tpo" ".deps/fgrun_pty.Po"; \
else rm -f ".deps/fgrun_pty.
Arthur Wiebe a écrit :
I must say that fgrun looks like a lot of bad coding to me. After
doing what you said that file compiled but then I got this error:
Making all in src
make all-am
if g++ -DHAVE_CONFIG_H -I. -I. -I. -I/FlightGear/include -g -O2 -MT
fgrun_pty.o -MD -MP -MF ".deps/fgrun_pty.T
I must say that fgrun looks like a lot of bad coding to me. After
doing what you said that file compiled but then I got this error:
Making all in src
make all-am
if g++ -DHAVE_CONFIG_H -I. -I. -I. -I/FlightGear/include -g -O2 -MT
fgrun_pty.o -MD -MP -MF ".deps/fgrun_pty.Tpo" \
-c -o fgrun_pt
As far as I know, there is no fgrun list, so post here.
it looks like your implementation of termios.h is incomplete.
try changing the line :
term.c_oflag &= ~( OLCUC | ONLCR );
by
term.c_oflag &= ~ONLCR;
-Fred
Arthur Wiebe wrote :
Should I post it here or in the fgrun mailing list? I assume here
s
Should I post it here or in the fgrun mailing list? I assume here
since there's only one person subscribed to the fgrun list.
I was getting this error:
if g++ -DHAVE_CONFIG_H -I. -I. -I. -I/FlightGear/include -g -O2 -MT
run_posix.o -MD -MP -MF ".deps/run_posix.Tpo" \
-c -o run_posix.o `test
Arthur Wiebe wrote :
I couldn't get fgrun to compile on OSX and so have started to write
one that's OS X native using Cocoa and AppleScript. (Applescript
Studio)
You should try to share your experience / problems with fgrun in order
to get help. I can check your patches if you have some.
-Fred
_
My package actually does not use a .fgfsrc file. It passes the flags
straight to fgfs.
And I don't understand resource forks either. And have never worked with them.
I couldn't get fgrun to compile on OSX and so have started to write
one that's OS X native using Cocoa and AppleScript. (Applescript
Double-clicking the icon isn't the problem. In many cases, getting the
.fgfsrc file properly installed was the problem. For my next release,
I was going to include a python script that would set up the file and
modify the default resource file. Many Mac users that subscribe to the
Users mail
On Sat, 18 Dec 2004 01:43:04 +0100, Arnt Karlsen <[EMAIL PROTECTED]> wrote:
> On Fri, 17 Dec 2004 16:55:26 -0500, Arthur wrote in message
> <[EMAIL PROTECTED]>:
>
> > I have built an application bundle of FlightGear for Mac OS X. It's a
> > rather large application because it includes everything s
On Fri, 17 Dec 2004 16:55:26 -0500, Arthur wrote in message
<[EMAIL PROTECTED]>:
> I have built an application bundle of FlightGear for Mac OS X. It's a
> rather large application because it includes everything such as the
> base data, fgfs, etc. Compressed it's a total of 132 MB.
>
> I have no
htGear developers discussions
> > <[EMAIL PROTECTED]>
> > Date: Fri, 17 Dec 2004 18:07:26 -0600
> > To: FlightGear developers discussions <[EMAIL PROTECTED]>
> > Subject: Re: [Flightgear-devel] FlightGear Mac OS X Application Bundle
> > Available
> >
Fri, 17 Dec 2004 18:07:26 -0600
> To: FlightGear developers discussions <[EMAIL PROTECTED]>
> Subject: Re: [Flightgear-devel] FlightGear Mac OS X Application Bundle
> Available
>
> That is not necessarily the case. I have had a heck of a time
> explaining to users how to get
lol, How many different ways can you explain to somebody how to double
click an icon.
On Fri, 17 Dec 2004 18:07:26 -0600, Jonathan Polley <[EMAIL PROTECTED]> wrote:
> That is not necessarily the case. I have had a heck of a time
> explaining to users how to get the application to run.
>
> On De
That is not necessarily the case. I have had a heck of a time
explaining to users how to get the application to run.
On Dec 17, 2004, at 6:04 PM, Arthur Wiebe wrote:
It's a single application in a disk image. No instructions included. I
figured anyone downloading FlightGear would know what to do
It's a single application in a disk image. No instructions included. I
figured anyone downloading FlightGear would know what to do with it.
By the way Curt, it's done uploading.
On Fri, 17 Dec 2004 17:50:23 -0600, Jonathan Polley <[EMAIL PROTECTED]> wrote:
> Arthur,
>
> Considering the prob
Arthur,
Considering the problems some people have been having in running the Mac
version, have you added instructions to the .dmg file? I was able to host the
previous version (0.9.6) on my .mac account, but it was less than 125 MB (which
is my limit).
Jonathan Polley
On Friday, Decembe
I have built an application bundle of FlightGear for Mac OS X. It's a
rather large application because it includes everything such as the
base data, fgfs, etc. Compressed it's a total of 132 MB.
I have no place to host such large files so I've made it available via
BitTorrent. I've attached it to
18 matches
Mail list logo
