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

Updating SCons from 3.1.2 to 4.0.0 is broken #20

Closed
LunarWatcher opened this issue Jul 8, 2020 · 1 comment
Closed

Updating SCons from 3.1.2 to 4.0.0 is broken #20

LunarWatcher opened this issue Jul 8, 2020 · 1 comment

Comments

@LunarWatcher
Copy link
Owner

here we go again...

SCons 4.0.0 was recently released, but in an issue in the SCons repo (3736), an update issue was pointed out that breaks the entirety of SCons, and by extension, Taskranger's build process. This is a Windows-only problem, because the filesystem is case-insensitive and doesn't allow SCons and scons. Linux and Mac remains unaffected.

The workaround is renaming the scons package folder to SCons. C:\python38\lib\site-packages\scons is one example of where it's found - this obviously depends on whether virtualenv is used or not, and what version of python, etc. Use some common sense when locating the directory.

I have no idea what consequences renaming has (if any), but the directory can always be purged manually if necessary.

@LunarWatcher
Copy link
Owner Author

The upstream solution is a complete reinstall. Nothing more will be done

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

No branches or pull requests

1 participant