-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make xygine depend on a release build of Box2D (preferably 2.3.2) #21
Comments
This is caused by version mismatches of the dependencies. The SFML errors appeared with the release of 2.4.1, reverting to 2.4.0 should fix these. Currently I'm waiting on the 2.4.2 release before modifying xygine. Box2D is a slightly different problem, however, caused by the fact I used a revision newer than the latest official release (which was 2.3.2 iirc) that breaks the API. I should address this by making xygine depend on the 2.3.2 release of Box2D rather than an arbitrary revision of the repo |
For anyone wishing to work around this until it is fixed erincatto/box2d@2cb4e26 has been tested to work |
Hi, I am getting this error on Mac OS while linking. I checked at the work around above but src/physics/PhysicsJointWheel.cpp does not seem to be updated. Undefined symbols for architecture x86_64: |
How odd. The wheel joint update was in this commit - dated 4 days before the work-around commit. Did you check out all the files to that revision or just the debug-draw files? |
Thanks. I did not get all the files. On a seperate note, I took the latest master build of xygine and getting this error.. /Users/Projects/xygine/xyginext/src/network/NetHost.cpp:128:21: error: no member named 'connectedPeers' in |
OK glad the box2D issue is working. I've moved the enet one to #43 |
Getting some build errors in g++ 5.4.1 on Linux; just wanted to make you aware just in case you weren't already. I can create a pull request if you like but most likely won't be able to until the weekend.
I'm also getting some warnings - I can put those into a separate issue if you like or just create a pull request in the future.
The text was updated successfully, but these errors were encountered: