-
Notifications
You must be signed in to change notification settings - Fork 1
feat: add pure build examples #10
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Error message: ``` ModuleNotFoundError: No module named 'quotes_app_python' ``` I also had to modify the `hook.on-activate` script so that it wouldn't generate error messages at runtime. `FLOX_ENV_CACHE` isn't populated in builds, so Poetry was attempting to create virtual environments under `/poetry/virtualenvs`.
Error message: ``` quotes-app-jvm-pure> 00:00:00.272661 FAILURE: Build failed with an exception. quotes-app-jvm-pure> 00:00:00.272706 quotes-app-jvm-pure> 00:00:00.272762 * What went wrong: quotes-app-jvm-pure> 00:00:00.272851 Gradle could not start your build. quotes-app-jvm-pure> 00:00:00.272951 > Could not initialize native services. quotes-app-jvm-pure> 00:00:00.273157 > Failed to load native library 'libnative-platform.dylib' for Mac OS X aarch64. ``` This appears to be a permissions issue with Gradle trying to get files outside of the repository: https://stackoverflow.com/questions/48652914/nix-gradle-dist-failed-to-load-native-library-libnative-platform-so-for-linu
Note that this loops over an array of "build modifiers", which is just a list of strings that get appended to the name of the environment, which also happens to be the name of the build. That's getting a bit overloaded, but not a priority at the moment. This also adds a list of "fixme" builds, which are skipped for now because they don't work. There's enough in-flight at the moment that I'd prefer to get the working pure builds in and come back to the problem builds once the release blockers are out of the way.
This adds GCC as a runtime dependency for the Rust pure build on Linux. This makes the build pass, but I don't think the executable should actually depend on GCC.
This build fails because the impure vendoring build cannot be accessed in the pure build: ``` quotes-app-go-pure> 00:00:00.002025 + stat /nix/store/sfglcsl9l0hgvlsl5bxr4nqb95ag9q7l-deps-0.0.0 quotes-app-go-pure> 00:00:00.002741 stat: cannot statx '/nix/store/sfglcsl9l0hgvlsl5bxr4nqb95ag9q7l-deps-0.0.0': No such file or directory ```
stahnma
approved these changes
Jun 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
chore: add failing Go pure build
This build fails because the impure vendoring build cannot be accessed
in the pure build:
fix: make Rust pure build pass
This adds GCC as a runtime dependency for the Rust pure build on Linux.
This makes the build pass, but I don't think the executable should
actually depend on GCC.
feat: ensure pure builds are run by make
Note that this loops over an array of "build modifiers", which is just
a list of strings that get appended to the name of the environment,
which also happens to be the name of the build. That's getting a bit
overloaded, but not a priority at the moment.
This also adds a list of "fixme" builds, which are skipped for now
because they don't work. There's enough in-flight at the moment that I'd
prefer to get the working pure builds in and come back to the problem
builds once the release blockers are out of the way.
feat: add pure build for C++
chore: upgrade packages in C++ example
chore: FIXME pure build failure for JVM
Error message:
This appears to be a permissions issue with Gradle trying to get files
outside of the repository:
https://stackoverflow.com/questions/48652914/nix-gradle-dist-failed-to-load-native-library-libnative-platform-so-for-linu
chore: upgrade packages in JVM example
feat: add pure build for ruby example
chore: upgrade packages in ruby example
chore: FIXME runtime failure for python pure build
Error message:
I also had to modify the
hook.on-activatescript so that it wouldn'tgenerate error messages at runtime.
FLOX_ENV_CACHEisn't populated inbuilds, so Poetry was attempting to create virtual environments under
/poetry/virtualenvs.chore: upgrade packages in python example
feat: add pure build for php
chore: upgrade packages in php example
feat: add pure build for nodejs
chore: upgrade packages in nodejs example
feat: add pure build for go
chore: upgrade packages in go example
feat: add pure build for rust
chore: upgrade packages in rust example