| Age | Commit message (Collapse) | Author |
|---|
|
Contributes to CURA-9365
|
|
Should be an acceptable workaround for pyinstaller/pyinstaller#6612
The `assemble` method is probably to0 specific to contribute with
a PR against PyInstaller.
Contributes to CURA-9365
|
|
Contributes to CURA-9365
|
|
Contributes to CURA-9365
|
|
pyinstaller doesn't play nice with MacOS Apps and codesigning.
https://developer.apple.com/library/archive/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG206
The following personal fork should provide a quick fix for this even
though pyinstaller still doesn't fully adhere to the file structure
specified by Apple.
See branch: https://github.com/jellespijker/pyinstaller@binaries_in_frameworks
Once this has been tested and verified to work I will open up
a PR against the pyinstaller repo.
Contributes to CURA-9365
|
|
Contributes to CURA-9365
|
|
Although net technically needed by Cura, our other Python binding
modules (such as pynest2d, pyArcus, pySavitar) might need it if
the need to be build on the host machine
Contributes to CURA-9365
|
|
Our requirements.txt was never fully utilized.
For our builds we use a requirements.txt
specified in the cura-build-enviroment repo.
But that file contained all the Python requirements
including, testing and dev tools.
This requirements.txt should contain the bare minimum
for running Python. Since these dependencies are shipped
we need to specify the hashes as well.
These hashes aren't necessary for build and test requirements
Contributes to CURA-9365
|
