pyallegro-general

[Pyallegro] So how do I use that?

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

Hello.

I am trying to get something in python using allegro, but some things seem
to be broken. I tried running ./setup install, and I get some problems
compiling _alpymodule.c (patch attached to compile properly). Then,
I get some weird messages from setup.py:

[gregorio:69] [~/cvs/libs/pyallegro]$ ./setup.py install
running install
running build
running build_py
warning: build_py: file a.py (for module a) not found
warning: build_py: file l.py (for module l) not found
warning: build_py: file p.py (for module p) not found
warning: build_py: file y.py (for module y) not found
warning: build_py: file a.py (for module a) not found
warning: build_py: file l.py (for module l) not found
warning: build_py: file p.py (for module p) not found
warning: build_py: file y.py (for module y) not found
running build_ext
skipping '_alpy' extension (up-to-date)
running install_lib
not copying build/lib.linux-i686-1.5/_alpy.so (output up-to-date)

Any help with that?

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

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

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

On Fri, Dec 14, 2001 at 11:18:07PM +0100, Grzegorz Adam Hankiewicz wrote:
> I get some weird messages from setup.py:
> 
> [gregorio:69] [~/cvs/libs/pyallegro]$ ./setup.py install
> running install
> running build
> running build_py
> warning: build_py: file a.py (for module a) not found
> warning: build_py: file l.py (for module l) not found
> warning: build_py: file p.py (for module p) not found
> warning: build_py: file y.py (for module y) not found
> warning: build_py: file a.py (for module a) not found
> warning: build_py: file l.py (for module l) not found
> warning: build_py: file p.py (for module p) not found
> warning: build_py: file y.py (for module y) not found
> running build_ext
> skipping '_alpy' extension (up-to-date)
> running install_lib
> not copying build/lib.linux-i686-1.5/_alpy.so (output up-to-date)

Ok, so I get those warnings both with python 1.5 and 2.1, which means that
alpy won't be installed. However I can force to use it running python
from that directory.  It doesn't work with 1.5 (hopefully this had been
documented before I tried it), and 2.1 just gives a weird message and
exists when I try to use allegro_init.

[gregorio:6] [~/cvs/libs/pyallegro]$ python
Python 1.5.2 (#0, Dec 27 2000, 13:59:38)  [GCC 2.95.2 20000220 (Debian GNU/Linux)] on linux2
Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam
>>> import alpy
Traceback (innermost last):
  File "<stdin>", line 1, in ?
  File "alpy.py", line 23, in ?
    import _alpy, sys
ImportError: /usr/lib/python1.5/site-packages/_alpy.so: undefined symbol: PyObject_DEL

[gregorio:7] [~/cvs/libs/pyallegro]$ python2.1
Python 2.1.1 (#1, Aug 25 2001, 15:17:34)
[GCC 2.95.2 20000220 (Debian GNU/Linux)] on linux2
Type "copyright", "credits" or "license" for more information.
>>> import alpy
>>> alpy.allegro_init()
>>> Temporizador
and here the interactive sesion ends.

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

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

[Juha-Matti T. <jm...@pu...>]

On ke, 2001-12-19 at 23:20, Grzegorz Adam Hankiewicz wrote:
> Ok, so I get those warnings both with python 1.5 and 2.1, which means that
> alpy won't be installed. However I can force to use it running python
> from that directory.  It doesn't work with 1.5 (hopefully this had been
> documented before I tried it), and 2.1 just gives a weird message and
> exists when I try to use allegro_init.

I had previously similar trouble, but I managed to get the stuff
installed when running setup as root. Could this problem be about this?

But there is something odd with the setup.py and/or distutils.

> ImportError: /usr/lib/python1.5/site-packages/_alpy.so: undefined symbol: PyObject_DEL

That's odd. I'll try to update my python debs and see if I can do
something about this.

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

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

On Thu, Dec 20, 2001 at 10:19:49PM +0200, Juha-Matti Tapio wrote:
> I had previously similar trouble, but I managed to get the stuff
> installed when running setup as root. Could this problem be about this?

Output/effect remains the same as root or user. Same messages with both
python versions (1.5 and 2.1).

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

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

[Juha-Matti T. <jm...@pu...>]

On to, 2001-12-20 at 23:29, Grzegorz Adam Hankiewicz wrote:
> On Thu, Dec 20, 2001 at 10:19:49PM +0200, Juha-Matti Tapio wrote:
> > I had previously similar trouble, but I managed to get the stuff
> > installed when running setup as root. Could this problem be about this?
> Output/effect remains the same as root or user. Same messages with both
> python versions (1.5 and 2.1).

Just a thought. Do you have python-dev package installed?

Currently the cvs-version seems to build nicely with the newest 2.1 and
2.2 Debian packages.


-- 
Juha-Matti Tapio, ATK-suunnittelija, fil. yo.
+358-50-5419230

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

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

On Tue, Jan 01, 2002 at 10:45:43PM +0200, Juha-Matti Tapio wrote:
> > Output/effect remains the same as root or user. Same messages with both
> > python versions (1.5 and 2.1).
> 
> Just a thought. Do you have python-dev package installed?

Yes. The only problem is with installation: only _alpy.so get's installed,
none other files are copied anywhere. The same happens with python 2.1,
which I installed from source, but there's just one big source file to
download from www.python.org, so I guess I don't need anything more.

> Currently the cvs-version seems to build nicely with the newest 2.1 and
> 2.2 Debian packages.

Yes. Please put somewhere (maybe that lone README?) that those versions
are required to run:

Python 1.5.2 (#0, Dec 27 2000, 13:59:38)  [GCC 2.95.2 20000220 (Debian GNU/Linux)] on linux2
Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam
>>> import alpy
Traceback (innermost last):
  File "<stdin>", line 1, in ?
  File "alpy.py", line 23, in ?
    import _alpy, sys
ImportError: /usr/lib/python1.5/site-packages/_alpy.so: undefined symbol: PyObject_DEL
>>>

Python 2.1.1 (#1, Aug 25 2001, 15:17:34)
[GCC 2.95.2 20000220 (Debian GNU/Linux)] on linux2
Type "copyright", "credits" or "license" for more information.
>>> import alpy
>>> print alpy.install_allegro
<function install_allegro at 0x8174afc>
>>>

BTW, I figured out that Allegro just doesn't work with interactive python
sessions (at least for me), because I tried to build my own pyallegro
version from scratch. However, the following script doesn't work as
expected for me:

#!/usr/bin/env python2.1

from alpy import *

install_allegro(SYSTEM_AUTODETECT)
install_keyboard()
print "Hey man"
print set_gfx_mode(GFX_AUTODETECT, 320, 200)
readkey()

I would expect it to set a graphic mode, but it doesn't, it prints
None. readkey works though.

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

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

[Juha-Matti T. <jm...@pu...>]

On ti, 2002-01-01 at 23:49, Grzegorz Adam Hankiewicz wrote:
> On Tue, Jan 01, 2002 at 10:45:43PM +0200, Juha-Matti Tapio wrote:
> > > Output/effect remains the same as root or user. Same messages with both
> > > python versions (1.5 and 2.1).
> > 
> > Just a thought. Do you have python-dev package installed?
> Yes. The only problem is with installation: only _alpy.so get's installed,
> none other files are copied anywhere. 

How does it react to "setup.py install_lib"?

> > Currently the cvs-version seems to build nicely with the newest 2.1 and
> > 2.2 Debian packages.
> Yes. Please put somewhere (maybe that lone README?) that those versions
> are required to run:

Done.

> #!/usr/bin/env python2.1
> from alpy import *
> install_allegro(SYSTEM_AUTODETECT)
> install_keyboard()
> print "Hey man"
> print set_gfx_mode(GFX_AUTODETECT, 320, 200)
> readkey()

> I would expect it to set a graphic mode, but it doesn't, it prints
> None. readkey works though.

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

What happens, if you do this:

from alpy ipmort *
import _alpy
install_allegro(SYSTEM_AUTODETECT)
install_keyboard()
_alpy.set_gfx_mode(GFX_AUTODETECT, 320, 200)
readkey()

It might give a more precise error message.

-- 
Juha-Matti Tapio, ATK-suunnittelija, fil. yo.
+358-50-5419230

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/