Complete.Org: Mailing Lists: Archives: freeciv-dev: December 1999:
[Freeciv-Dev] Re: jjm: Multi-client configure support added.
Home

[Freeciv-Dev] Re: jjm: Multi-client configure support added.

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: jjm: Multi-client configure support added.
From: Jeff Mallatt <jjm@xxxxxxxxxxxx>
Date: Wed, 29 Dec 1999 09:53:09 -0500

Given what David has told me, I changed the multi-client configure support
to prefer Xaw3d over Xaw when guessing.

At 1999/12/28 07:51 , David Pfitzner wrote:
>Jeff Mallatt wrote:
>> At 1999/12/28 06:41 , David Pfitzner wrote:
>> >It used to be that the "best guess" would use Xaw3d if available,
>> >in preference to plain Xaw (if Gtk+ not available).  The new setup 
>> >doesn't seem to do this.  I think it would be good to do something
>> >like this, to try to reduce the occurence of Xaw variants problems.
>> I figured that the vanilla Xaw would be less inclined to "Xaw variants
>> problems" than Xaw3d.
>
>My understanding is that for Xaw, two common system 
>configurations are:
>  1. have plain Xaw only;
>  2. have Xaw and Xaw3d.
>In case 1, configure with fail to find Xaw3d (if it looks), so 
>will only build as plain Xaw, and will work fine. 
>
>In case 2, configure will "find" Xaw, and compile, but 
>typically will actually link to Xaw3d, and will segfault at 
>runtime.  In this case configure will also find Xaw3d if it
>explicitly looks for Xaw3d, and if compiled and linked 
>explicitly for Xaw3d, everything will work fine. 
>
>So its better to use Xaw3d explicitly if it is found.

Attachment: config-defualt-xaw3d.diff.gz
Description: Binary data

jjm

[Prev in Thread] Current Thread [Next in Thread]