Skip to content
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

Updated instructions for Pypy on Ubuntu/Linux #59

Merged
merged 27 commits into from
Mar 7, 2019

Conversation

krs013
Copy link
Collaborator

@krs013 krs013 commented Mar 7, 2019

Addresses #16

I tested and updated the installation instructions for Pypy on Ubuntu. This was done on a pristine Ubuntu 18.04 LTS VM, so the dependencies are definitely enough to get things running.

This does not involve Portable Pypy, though I did test it and found that it could not install the dependencies because it wasn't configured by default to look at the system paths. It is still likely that alternate instructions could be provided for normal (not portable) installations of Pypy 7.0, or that we could figure out how to get Portable Pypy to compile against the system libraries (though that kindof defeats the purpose of it). However, I don't notice any speed difference between Pypy 5.1 (Linux) or Pypy 7.0 (macOS host). I also think it's beyond the scope of this project. Personally, I would rather try to eliminate or make optional imageio and numpy as dependencies so there wouldn't be a need for so many system libraries (although I'm not sure if that would fix things for libsdl2-dev).

Oh, and I changed the instructions to put the virtualenv in the root PyBoy folder instead of Source, because Source was feeling a bit cluttered and putting the venv in Source named it (Source) instead of (PyBoy) which is nicer.

…he window. So far I only implemented tiles, and that doesn't work anyway. It's also tremendously slow.
…!= x*4 bc you still have the low bits) and now it seems to work, but still really slowly, and just tiles
…ve spent too long on embedded platforms to know that they're not better. The original math was easier to follow
…mpts failed so it probably won't get much faster without big changes.
… changes that shouldn't have been merged back into master)
…ot a blank screen, threw off the tests for a while)
@krs013
Copy link
Collaborator Author

krs013 commented Mar 7, 2019

I'm not sure why it lists so many commits... could I have updated my fork wrong?

@Baekalfen
Copy link
Owner

Hmm. I think you should have done some rebasing. But I think it is ok, if I squash and merge.

@Baekalfen Baekalfen merged commit 4c1aaaa into Baekalfen:master Mar 7, 2019
@krs013 krs013 deleted the pypy-linux branch March 7, 2019 18:09
@krs013
Copy link
Collaborator Author

krs013 commented Mar 7, 2019

That's what I get for leaving local changes on my master branch. I did a reset --hard upstream/master and will keep my work in other branches from now on so this shouldn't happen again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants