You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: