Re: [Pyallegro] So how do I use that?

[Grzegorz A. H. <gr...@te...>]

On Wed, Jan 02, 2002 at 12:46:59AM +0200, Juha-Matti Tapio wrote:
> How does it react to "setup.py install_lib"?

Wait a moment please... I am eating my hat by now... (munch munch).

I am sorry, just forgot to update my cvs copy so I had not been running
the latest code: I've been reportin ghosts. Now everything works cleanly
for python2.1, and for python1.5 the only glitch is:

[~/cvs/libs/pyallegro]$ ./setup.py build
running build
running build_py
not copying alpy.py (output up-to-date)
running build_ext
building '_alpy' extension
gcc -g -O2 -fPIC -I/usr/local/include -I/usr/include/python1.5 -c _alpymodule.c -o build/temp.linux-i686-1.5/_alpymodule.o
_alpymodule.c: In function `blend_driver':
_alpymodule.c:3450: warning: assignment discards qualifiers from pointer target type
_alpymodule.c: In function `alpy_create_color_map':
_alpymodule.c:3502: `PyExc_Warning' undeclared (first use in this function)
_alpymodule.c:3502: (Each undeclared identifier is reported only once
_alpymodule.c:3502: for each function it appears in.)
error: command 'gcc' failed with exit status 1

> Currently set_gfx_mode() returns always None. Instead it raises
> AlpyException when it failes to set the mode.

The error was caused by using old code. Now, for example exhello.py
doesn't work under console but does under X. Explanation: it has something
to do with paths, since I am using fbdev and this driver is compiled as an
allegro module. Where should I look at to fix this? The example just fails
with GFX_SAFE. On my computer the only driver which works under console
is framebuffer, and it was me who wrote it's GFX_SAFE behaviour, so I know
for sure it's a module loading issue, allegro C examples work perfectly.

-- 
 Grzegorz Adam Hankiewicz   gr...@te...   http://gradha.infierno.org/