We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When running make (https://github.com/JeanChristopheMorinPerso/otio-wasm/blob/main/.github/workflows/deploy.yaml#L36), we could probably set PYODIDE_PACKAGES to an empty list. See https://pyodide.org/en/latest/development/building-from-sources.html#partial-builds. I could simply just dun PYODIDE_PACKAGES=opentimelineio make.
make
PYODIDE_PACKAGES
PYODIDE_PACKAGES=opentimelineio make
Also, why is cmake spending so much time at the check step (https://github.com/JeanChristopheMorinPerso/otio-wasm/runs/6840255883?check_suite_focus=true#step:7:282) ?
The text was updated successfully, but these errors were encountered:
Cmake is spending time doing:
-- Performing Test HAS_FLTO -- Performing Test HAS_FLTO - Success -- Performing Test HAS_FLTO_THIN
Sorry, something went wrong.
No branches or pull requests
When running
make
(https://github.com/JeanChristopheMorinPerso/otio-wasm/blob/main/.github/workflows/deploy.yaml#L36), we could probably setPYODIDE_PACKAGES
to an empty list. See https://pyodide.org/en/latest/development/building-from-sources.html#partial-builds. I could simply just dunPYODIDE_PACKAGES=opentimelineio make
.Also, why is cmake spending so much time at the check step (https://github.com/JeanChristopheMorinPerso/otio-wasm/runs/6840255883?check_suite_focus=true#step:7:282) ?
The text was updated successfully, but these errors were encountered: