Mail Archives: djgpp/1998/10/31/12:48:40
Thanks, Martin. This is just the sort of technical insight I'm
looking for.
May I comment on a few points you made and have your
response?
At 03:06 PM 10/31/98 GMT, you wrote:
>I don't think Allegro is a port. A port is something that has been
>developed for one system and/or OS, and then moved/generalised/made to
>work on another system and/or OS. I think Allegro was developed
>originaly for DJGPP, hence it's not a port.
I get it. Yes, this is true.
>However all(?) the GNU program were originaly developed for Unix
>system and later on made to work on *DOZE, hence they are ports.
Does the program have to have been a GNU program originally to
be a port? I don't think so. I may be wrong. Please correct me.
Of course, you may have already answered this below.
>As long as you have a working program that works on a new system
>and/or OS then IMHO you _have_ a port. Although the explanations how
>to compile the program are so lacking it's not easily recompiled by
>another person, you still have a port. The thing to do here I'd think
>is to give feedback to the porter that he should include some better
>instructions and what they should be.
Okay, you will have a port after doing a lot of work.
What you had to begin with was not a port but a ___________???????.
>Well, find and read all the documentation regarding the port is the
>methodology. Then just whack-whack-whack on the code until it
>compiles... And works... Or perhaps a mail to the porter or this
>mailing list?
Good point. I get embarrassed with some things. Next time I will
try and see.
Ralph
Ralph Proctor
Coral Gables, Florida
ralphgpr AT shadow DOT net
- Raw text -