public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Skeezics Boondoggle <skeezics@q7.com>
To: xconq7@sources.redhat.com
Subject: Re: SDL Interface Development
Date: Sun, 31 Oct 2004 16:28:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0410310142380.5719-100000@q7.q7.com> (raw)
In-Reply-To: <41841290.3040905@phy.cmich.edu>

On Sat, 30 Oct 2004, Eric McDonald wrote:

[snip]
>    A while back ago, we considered SDL_Pango for handling of 
> international and exotic text. Pango (which SDL_Pango obviously 
> requires) is not without dependencies either. So I think point (2) is 
> something worth considering. How much should Xconq be able to stand 
> alone? And how much should we cave in to rapid development at the 
> expense of raising the hacker "cost of entry", so to speak?
[snip]

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.  I'd say if it's smaller/easier to
bundle those libs with the Xconq sources and build them all in one shot,
that's fine, or we'd need to make sure that the configure script can
easily find them (or be told where to find them) already installed on the
system.

Having lived through the years when "all the world's a Vax", then the
period of "all the world's a Sun" and now "all the world's the hacked up
one-off peculiar Linux box on my desk", I'm just *reeeeeally* tired of
constantly screwing around with and patching configure scripts that assume
too much.  That's my only worry with using third party libs that come with 
a mile-long dependency list...

Also, I've been remiss in building xconq from the latest CVS snapshots for
Solaris... I think something was broken the last time I tried it... oh
geez, almost a year ago!  (November 15th, 2003)  I should grab the latest
sources and see if the existing stuff still builds on Solaris before
griping about possible future changes, eh? :-)

-- Chris

  parent reply	other threads:[~2004-10-31  8:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2004-10-31 19:04   ` Lincoln Peters
2004-10-31 19:50     ` Skeezics Boondoggle
2004-10-31 19:04   ` Eric McDonald
2004-11-07  8:29 ` Publicity Test Run Elijah Meeks
2004-11-13 23:23   ` New Source Tarball and Windows Installer (was Re: Publicity Test Run) Eric McDonald
2004-11-13 23:55   ` Publicity Test Run Lincoln Peters
2004-11-14  0:54     ` Eric McDonald
2004-11-14 22:31       ` Lincoln Peters
2004-10-31 17:45 Re: SDL Interface Development ejessen
2004-10-31 18:08 ` D. Cooper Stevenson
2004-10-31 18:57   ` Lincoln Peters
2004-10-31 19:09 ` Eric McDonald

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=Pine.LNX.4.44.0410310142380.5719-100000@q7.q7.com \
    --to=skeezics@q7.com \
    --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).