public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: "D. Cooper Stevenson" <cstevens@gencom.us>
To: xconq7@sources.redhat.com
Subject: Re: SDL Interface Development
Date: Sun, 31 Oct 2004 18:08:00 -0000	[thread overview]
Message-ID: <200410311748.51902.cstevens@gencom.us> (raw)
In-Reply-To: <20041031162812.SIHQ2188.mta11.adelphia.net@mail.adelphia.net>

On Sunday 31 October 2004 16:28, ejessen@adelphia.net wrote:
> [not including the libraries in the build raises] the barrier to entry so 
high, that 
> nobody but the most fanatical will attempt to maintain
> the code.  Which means the program will die out when
> the fanatics move on.

Insightful. 

On Sunday 31 October 2004 08:52, Skeezics Boondoggle wrote:
> Just to chime in from the Solaris camp - this all sounds great, as long as
> the dependent libraries are reasonably cross-platform and the build for
> non-Linux/Windows machines (is that the diplomatic way to say "real Unix"
> machines? :-) doesn't become untenable.

Absolutely. 

Here's a quick 'fact check' listing the library dependancies and weather or 
not they currently support Linux, Sun, and Windows platforms:

Libary           Linux         Mac 9        Mac OSX        Sun        Windows
------           -----         ------      ---------      -----      ---------

libsdl             X              X            X            X           X
paragui            X              X            X            ?           X
FreeType           X              X            X            X           X
Zlib               X              ?            ?            ?           X
libpng             X              X            X            X           X
SDL_Image          X              X            X            X           X
Expat              X              X            X            X           X
OpenGL             X              X            X            X           X

I was conservative. I'm pretty confident that Zlib is supported by Sun :). 
Overall my impression is that ParaGUI is careful about cross-platform 
compatibility.

Please modify as necessary.

-Coop


  reply	other threads:[~2004-10-31 17:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-31 17:45 ejessen
2004-10-31 18:08 ` D. Cooper Stevenson [this message]
2004-10-31 18:57   ` Lincoln Peters
2004-10-31 19:09 ` Eric McDonald
  -- strict thread matches above, loose matches on Subject: below --
2004-10-30 23:28 Eric McDonald
2004-10-31  4:10 ` Lincoln Peters
2004-10-31  6:13   ` Eric McDonald
2004-10-31  6:34     ` Elijah Meeks
2004-10-31  7:34       ` Lincoln Peters
2004-10-31 18:39         ` Eric McDonald
2004-10-31 18:23       ` Eric McDonald
2004-10-31  6:54 ` D. Cooper Stevenson
2004-10-31 18:26   ` Eric McDonald
2004-10-31 16:28 ` Skeezics Boondoggle
2004-10-31 19:04   ` Eric McDonald
2004-10-31 19:04   ` Lincoln Peters
2004-10-31 19:50     ` Skeezics Boondoggle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200410311748.51902.cstevens@gencom.us \
    --to=cstevens@gencom.us \
    --cc=xconq7@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).