Re: [AD] Allegro on amd64-linux |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] Allegro on amd64-linux
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Sun, 17 Oct 2004 16:21:09 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=JmAxLrIrwTdoalhkvYwf4cJf+5v4Wxg8UH9iknlUOCt3U7CdckLW/8lmSM97RDFvrcKUdnUlEyOrRXaXsEGcJXVBEyLBDJqOO28wY9dAuuJ+wCJ25SrizRntO2db3pYs5n4M6HjP7lDdUVLi4PmoLgy6HbDLNi40DrIYNhM3P5A
On Sun, 17 Oct 2004 19:42:09 +0200, Eric Botcazou
<ebotcazou@xxxxxxxxxx> wrote:
> Sorry, I missed it. Unfortunately, I don't think it is sufficient: did you
> try to compile the whole package with --disable-vga? exscroll and the test
> program will very likely still not compile with your patch.
exscroll and the test program behave perfectly. exscroll will first
try to set a Mode-X screen, and if that fails, it uses GFX_AUTODETECT.
The test program uses #ifdef's to be able to compare the driver ID,
then if that's true do some Mode-X specific stuff. Since the "extra"
code will only do anything if you're using the Mode-X driver, the mere
presence of the define changes nothing.
However, I just now did try compiling with --disable-vga and there was
a linking problem with test. Undefined reference to
split_modex_screen. So, I can either make it so the Mode-X functions
are exposed if GFX_MODEX is ever available (regardless if it's
settable, or I can change the test (and probably exscroll) to check
for GFX_HAS_MODEX instead. I'd prefer to do the former since I don't
think the GFX_HAS_* macros should be exposed to the API (since VGA,
ModeX, and VBEAF are the only drivers to have them).
- Kitty Cat