From: Grzegorz A. H. <gr...@ti...> - 2007-07-30 06:45:55
|
On 2007-07-29, Tristan Ankerstar <tr...@an...> wrote: > Hi. I'm part of a team putting together a game in python. We're > in the process of try to switch our graphics/gaming library > to allegro, and pyallegro (specifically alpy) looks like the > perfect tool. However... I can't seem to get it to compile. I > have python 2.4 installed, I have allegro 4.2 installed (both from > ubuntu debs) and I'm not a complete idiot, quite. However, well, > "python setup.py build" seems to fail horribly. I've attached the > output in a file. The attachment is missing or SF ate it. If you have problems sending the attachment try using SF's patch tracker or put it on some web. > Thanks! And thanks for the work, guys, this wrapper theoretically > makes decent development a whole lot more pleasant. Not to burst your bubble but alpy is quite crude, doesn't offer much advantage over the C api other than being used from a language more comfortable than C. The whole api is not wrapped: there are obvious stuff like 3d functions but others may have to be wrapped too. Please evaluate the whole thing with detail before proceeding, or you may have trouble later. Also, python is very bad with APIs that have to modify lots of memory buffers, so you should expect a slowdown from normal C code. |