Date: Tue, 12 Aug 2003 17:04:24 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Hans Lambermont <hans@lambermont.dyndns.org> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: sdl11-config / sdl-config Message-ID: <20030813000424.GA50252@rot13.obsecurity.org> In-Reply-To: <20030812215101.GH92209@moya.lambermont.dyndns.org> References: <20030811202331.GC92209@moya.lambermont.dyndns.org> <20030812034508.GA903@k7.mavetju> <20030812042553.GA45612@rot13.obsecurity.org> <20030812114430.GK815@k7.mavetju> <20030812213307.GG92209@moya.lambermont.dyndns.org> <20030812214420.GA49666@rot13.obsecurity.org> <20030812215101.GH92209@moya.lambermont.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--TB36FDmn/VVEgNH/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Aug 12, 2003 at 11:51:01PM +0200, Hans Lambermont wrote:
> Kris Kennaway wrote:
>=20
> > On Tue, Aug 12, 2003 at 11:33:07PM +0200, Hans Lambermont wrote:
> > > Edwin Groothuis wrote:
> > > > See also ports/55494: [patch] ports/Mk/bsd.sdl.mk
> > >=20
> > > That won't help me. I'm not talking about one of the ports, but of mo=
re
> > > generic software. For SDL in Blender we use things like :
> > >=20
> > > sdl-config --prefix
> > > sdl-config --libs
> > > sdl-config --cflags
> > >=20
> > > for all target platforms (around 10), except this doesn't work on
> > > FreeBSD because of the version number in the name ... hence my symlink
> > > proposal; it leaves sdl11-config as is for all ports to use, and still
> > > offers non-ports software a reasonable default. If both sdl11 and say
> > > sdl12 were installed I don't even care to which one it would point, i=
f I
> > > did I would be using sdl11-config. Ok, enough. what do you think now ?
> >=20
> > As I already said, patch the port to use ${SDL_CONFIG} instead of a
> > hard-coded binary name.
>=20
> Did you read what I wrote ? I am not talking about a port, so
> ${SDL_CONFIG} won't work for me. SDL made sdl-config and I think that
> should be available for non-port software.
And I have said earlier in this thread, that approach breaks down when
there are more than one version of SDL installed on the system. You
may not have had to deal with this kind of upgrade before, but we have
(sdl10 -> sdl11), and it's a pain in the ass because all sorts of
ports typically break when built with the new version, so there has to
be a simple mechanism in place to allow them to build with the old
one.
Preparing for it in advance by not hard-wiring things to only work
with a single concurrent SDL installation is the correct approach for
the long run. Otherwise, we'd just have to introduce it (again) the
next time a major SDL update comes out and all the ports that refer to
the sdl-config -> sdl13-config symlink fail to build.
Vendor software should be taught to do the following:
SDL_CONFIG?=3Dsdl-config
foo:
...${SDL_CONFIG} --libs...
So it works in the default SDL case as well as on FreeBSD.
At this point I think I've said everything I need to say about this
issue.
Kris
--TB36FDmn/VVEgNH/
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)
iD8DBQE/OYCIWry0BWjoQKURAsWuAJ9Kj7z8VcqOonloNJqnf/0YYU0adACgkltN
Noh8hAAVzXICDQJtaZh4Bpo=
=pdRF
-----END PGP SIGNATURE-----
--TB36FDmn/VVEgNH/--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030813000424.GA50252>