Problems setting up ballistica on windows #226
Unanswered
YashKandalkar
asked this question in
Q&A
Replies: 1 comment
-
Hmm yes I believe the asset build scripts set the output python files as read-only. I did this a while back to avoid accidentally editing scripts under build/ when I would be iterating and click on an error path. It would probably be fine to remove this code (or make it conditional on an environment variable) if you'd like to take a stab at it. Or I can keep it in mind and try to do it when I get a chance. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I followed the Editor Setup wiki for pycharm on windows.
I'm using WSL2 on windows and I've followed all the steps in Getting Started. The build (
make prefab-debug
) is successful the first time, but whenever I edit a file, save it and run the make command again, it gives this error:The files are write-protected after they are compiled, so rsync or even windows is not able to change it's permissions.
Also the py files I edit have
\r\n
line endings (I think) because the build is successful when I:set ff=unix
with vim and delete the corresponding pyc files.I have set the line endings to
\n
in PyCharm too.What am I doing wrong?
Beta Was this translation helpful? Give feedback.
All reactions