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
windows installation problems #104
Comments
Thanks. I've seen the PR. FYI, I love to have this working on windows, but I'm not sure anyone has tested it that much, so I expect you to hit some problems after it's installed. I'm happy to review and discuss any windows-related patches, but as I don't have easy access to a windows machine, I can't really test things myself that easily |
Cross platform testing is a pain. Usually that's what CI is for. Have you thought about using travis or appveyor? I'll spend some time looking into it and you can see if you like it. |
Oh, that would also be very welcome. I've been kicking myself for not doing unit testing from the beginning. Could have caught a lot of unnecessary errors that way. But just build/install testing with travis (or similar) would be great. |
Hopefully this should be fixed now. Would be great if you or someone else could confirm this. Thanks! |
Awesome! |
I ran into a few bumps trying out fusesoc, this is what I tried on a windows 10 machine with python 2.7.8
looks like setup.py put a file named fusesoc in C:/Python27/Scripts. Let's try running that.
It's confused. I decided to try inside of a virtual environment.
That got further. That one looks like a missing dependency
UPDATE:
I think I figured out the issue: https://python-packaging-user-guide.readthedocs.io/en/latest/distributing/#scripts
"Although setup() supports a scripts keyword for pointing to pre-made scripts to install, the recommended approach to achieve cross-platform compatibility is to use console_scripts entry"
I'm working on a fix
The text was updated successfully, but these errors were encountered: