Mail Archives: djgpp/2000/10/14/23:31:17
Do you use the more POSIX-ish functions directly, or do you have your own
abstraction layer (via. wrapper functions or #defines) to make portable
programs?
"Johan Henriksson" <jhe AT realsoftware DOT cjb DOT net> wrote in message
news:003f01c03608$472020a0$0500a8c0 AT brk...
>
> from: Johan Henriksson, leadprogrammer @ www.realsoftware.cjb.net
> "It is not the length of life that counts but what you make out of it" -
me
> --------------------------------------------------------------------------
--
> ------------
> >Hi all.
> >
> >Warning: these questions may appear slightly OT.
> OT questions are usually most interesting of some reason :/
>
> >I have been experimenting in compiling my DJGPP-intended programs using
gcc
> >in Linux. Unfortunately I'm having lots of trouble (this is not
alleviated
> >by the fact that I'm not Linux-adept).
> >
> >1. I have a disquieting feeling that doing graphics stuff in Linux is
> >tricky. For example when I try to run the examples that come with the
> >Allegro WIP, I get errors about Mode-X (this only happens for some of the
>
> I don't know if all funny Mode-X-stuff is supported on Linux. I don't
think
> so.
>
> >examples). Does a program need to do stuff with permissions in order to
> >change video mode, or something?
> Depends. This question should have been send to the Allegro mailinglist.
> For X (I think your programs should run in X), you can do w/o. But to
> access DGA, you need root-permissions.
>
>
> >2. Backslash-newlines, which i use occassionally for the more complicated
> >#defines, aren't recognised by cpp, apparently because of the CRLF
problem.
> >Is there a simple way I can get around this? I'd like to be able to
> compile
> >the same sources that I edit with RHIDE in dos.
>
> You're kidding??? I've never got this problem. Either try upgrading or
> use the utod/dtou-utilities
>
> >3. Lots of functions I use often in DJGPP, usually in connection with
> files,
> >simply don't exist in the linux library. (But I can get around this by
> >using more complicated things like fstat().) Still, the question
> remains...
>
> Simple solution: Don't use such functions. My games work in both Win32,
> X, Dos, Windows & BeOS simply because I make as little use of LibC
> as possible.
> And yes, you have to live with more advanced functions. itoa() doesn't
exist
> either
> so you have to sprintf()
>
- Raw text -