enroot
macos-cross-compiler
Our great sponsors
| enroot | macos-cross-compiler | |
|---|---|---|
| 3 | 4 | |
| 552 | 322 | |
| 4.0% | - | |
| 4.4 | 8.8 | |
| 4 days ago | 2 months ago | |
| Shell | Earthly | |
| Apache License 2.0 | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
enroot
-
Show HN: dockerc – Docker image to static executable "compiler"
Enroot can do something similar: https://github.com/NVIDIA/enroot/blob/v3.4.1/doc/cmd/bundle....
-
Researchers: Do you use idle computer labs as your cluster?
NVIDIA Enroot A lighter weight alternative to Singularity which solves a lot of issues in regards to user namespaces and subuid/subgid. Still evaluating.
-
Show HN: Vas-quod – A minimal Linux container runtime written in Rust
Enroot does exactly that: https://github.com/NVIDIA/enroot
macos-cross-compiler
-
I stopped worrying and loved Makefiles
Make is excellent if you use it properly to model your dependencies. This works really well for languages like C/C++, but I think Make really struggles with languages like Go, JavaScript, and Python or when your using a large combination of technologies.
I've found Earthly [0] to be the _perfect_ tool to replace Make. It's a familiar syntax (combination of Dockerfiles + Makefiles). Every target is run in an isolated Docker container, and each target can copy files from other targets. This allows Earthly to perform caching and parallelization for free, and in addition you get lots of safety with containerization. I've been using Earthly for a couple of years now and I love it.
Some things I've built with it:
* At work [1], we use it to build Docker images for E2E testing. This includes building a Go project, our mkdocs documentation, our Vue UI, and a ton of little scripts all over the place for generating documentation, release notes, dependency information (like the licenses of our deps), etc.
* I used it to create my macOS cross compiler project [2].
* A project for playing a collaborative game of Pokemon on Discord [3]
IMO Makefiles are great if you have a few small targets. If you're looking at more than >50 lines, if your project uses many languages, or you need to run targets in a Docker container, then Earthly is a great choice.
[0]: https://earthly.dev/
[1]: https://p3m.dev/
[2]: https://github.com/shepherdjerred/macos-cross-compiler
[3]: https://github.com/shepherdjerred/discord-plays-pokemon
-
Show HN: dockerc – Docker image to static executable "compiler"
It will depend heavily on the docker image you're trying to ship. For example with macos-cross-compiler[0] the resulting binary is over 2GB. With python:alpine[1] it's only 25MB.
Because image isn't copied whether the image is 2GB or 25MB the startup time will be nearly instantaneous for both.
The runtime adds 6-7MB of overhead although I expect that this can be reduced to less than 3MB with some work.
[0]: https://github.com/shepherdjerred/macos-cross-compiler
- So You Want to Ship a Command-Line Tool for macOS
- Show HN: macOS-cross-compiler – Compile binaries for macOS on Linux
What are some alternatives?
Squid - Squid Web Proxy Cache
dockerc - container image to single executable compiler
vas-quod - :aerial_tramway: Minimal linux container runtime
dockcross - Cross compiling toolchains in Docker images
railcar - RailCar: Rust implementation of the Open Containers Initiative oci-runtime