Open ThomasRahm opened 3 years ago
It's very kind to see how proactive you are with coming up with solutions to these problems and sharing them.
Change line one in env_win64.bat to
call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" amd64 8.1
As I understand from documentation, this causes it to use the Windows 8.1 SDK, but currently we can't do that since our build server is still Windows 7. We're working on a migration, but it's apparently a lot of work. Weird though that apparently using the most recent SDK would break the build process? Perhaps there is one such SDK version number that is available for Windows 7 as well. Perhaps @evtrados would like to know about this, as he's been on this issue recently.
Copy DLLs from cura-build-environment\lib\site-packages\numpy\core to cura-build-environment\lib\site-packages\numpy\DLLs The files seems to be moved away from there in projects/python_packages.cmake line 66ff.
Seems like we've more or less encountered the reverse. The DLLs need to be moved to the /core
directory because that's where cx_Freeze looks for them. See also https://github.com/marcelotduarte/cx_Freeze/issues/653 .
Issue 3 is indeed a known issue. It also happens for libArcus. It's not a problem in cura-build-environment but rather in those repositories itself. It's very annoying on Linux because the build then suddenly needs administrator access to install things into the Python dist-packages folder.
Issue 1:
Occurs when trying to build cura-build-environment:
Fix:
Change line one in env_win64.bat to
call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" amd64 8.1
Issue 2:
Happens when trying to start cura(
python Cura-4.9\cura_app.py --external-backend
) using compiled cura-build-environment (to supply the dependencies):Fix:
Copy DLLs from
cura-build-environment\lib\site-packages\numpy\core
tocura-build-environment\lib\site-packages\numpy\DLLs
The files seems to be moved away from there inprojects/python_packages.cmake
line 66ff.Issue 3:
If python 3.8 is already installed on the System, some of the Savitar module files are copied into the native python installation(for example in appData), and not into the target one(cbe_install_dir).
Fix:
Deinstalling python 3.8 from the system.
Result:
After these changes, the build environment seems to be working for me.