kne / pybox2d-from-googlecode

Automatically exported from code.google.com/p/pybox2d
Other
0 stars 0 forks source link

cannot build on os x #40

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. download svn
2. attempt to build

Did you check the issue list? pybox2d 2.0.2b1 is old, and some issues are
marked fixed (as in the SVN), but they have not been released yet.
yes

What is the expected output? What do you see instead?
lipo: can't figure out the architecture type of: /var/tmp//ccbzGtkX.out

What version of pybox2d are you using? On what operating system? 32-bit or
64-bit?
64

Please provide any additional information below.
cannot compile from svn.

i have a game written with pybox2d 2.02b2.  most people cannot get it compile 
under any circumstances.  on my system, i was able to get it to work after 
upgrading swig.  one user has the following error:

tried svn as well, will not build.

swigging Box2D/Box2D.i to Box2D/Box2D_wrap.cpp
swig -python -c++ -IBox2D -O -small -includeall -ignoremissing -w201 -outdir . 
-o Box2D/Box2D_wrap.cpp Box2D/Box2D.i
Box2D/Box2D_printing.i:29: Error: Syntax error in input(3).

Original issue reported on code.google.com by Leif.The...@gmail.com on 12 Apr 2011 at 12:04

GoogleCodeExporter commented 9 years ago
I believe an old version SWIG is the culprit in most cases. I can't fix 
something like the error you pasted, as there is no invalid syntax there.

If you can dig further into this issue, I would appreciate it. I no longer have 
access to an OSX machine to test.

Original comment by sir...@gmail.com on 12 Apr 2011 at 12:38

GoogleCodeExporter commented 9 years ago
I agree with SWIG being an issue.  Really, this is disorganized report.

The first issue comes from another user (i am relaying this to you) and the 
error that he sent me is included.  This is with the macports version of SWIG 
2.0.2.

I believe that this was a standard "python setup.py build".  I tried to 
duplicate this on my machine, but was unable to.

Original comment by Leif.The...@gmail.com on 12 Apr 2011 at 12:45

GoogleCodeExporter commented 9 years ago
I've never seen the first error, and unfortunately without a lot more 
information I can't say much about it.

Original comment by sir...@gmail.com on 12 Apr 2011 at 4:39