Curses, foiled again.

Thread View: comp.sys.acorn.tech

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Steve Loft Fri, 22 Jan 1993 17:32

#744

Author: Steve Loft
Date: Fri, 22 Jan 1993 17:32

15 lines
1279 bytes

Since no-one admitted to having ported curses, I decided to get hold of
GNU curses and have a bash myself, using UnixLib.  A little foolhardy,
as I haven't attempted anything like this before and I don't really know
what I'm doing.  As usual.  Anyway, I thought I'd throw the whole lot at
the compiler and see what happens.  It complains that it can't find
"sgtty.h", and sure enough I don't seem to have anything called that
anywhere on my disc.   Any suggestions as to what I can do now?  ("Give
up, you fool" is acceptable, and very tempting, although things did seem
to be going rather well up until this point).

Steve
-- 
|  Steve Loft                                  steve@klaatu.demon.co.uk   |
|  Doncaster,                                                             |
|  South Yorks.                                                           |

Re: Curses, foiled again.

#799

Author: R Voisey
Date: Thu, 28 Jan 1993 10:48

33 lines
1959 bytes

In article <727749140snx@klaatu.demon.co.uk> steve@klaatu.demon.co.uk writes:
>the compiler and see what happens.  It complains that it can't find
>"sgtty.h", and sure enough I don't seem to have anything called that

sgtty.h is an include file which usually just includes (into itself) the
system dependent headers concerned with talking to terminals.  I vaguely
recall that in unix ioctl.h is included, which contains mainly compiler
definitions (such as BELL 07 etc).  It also contains some very OS
dependent stuff such as socket support etc.

So, basically, it's specific to Unix (and a couple of similar OSs) so does
not appear in the standard Archimedes C library.  You'll have to remove
the #include <sgtty.h> statement, then run it through the compiler again
and see what it complains about.  I haven't seen the source in question, but
it's possible it just uses a few of the compiler definitions which you can
pick out of the throwback and derive yourself.  If, however, it expects to
use sockets, pipes and so forth you have a problem.

>Any suggestions as to what I can do now?  ("Give
>up, you fool" is acceptable, and very tempting, although things did seem
>to be going rather well up until this point).

I recall that somebody did a Unix library for the Arch, so maybe it will
make life easier (I haven't seen it).  If not, you're in for some fun I
suspect.

Cheers

Bob
-- 
  Robert J. Voisey  :  r_voisey@csd.uwe.ac.uk
         -- Probug Software Developments --
162 Staplehill Rd, Fishponds, Bristol, Avon, England

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads