|
You are here |
infinitedigits.co | ||
| | | | |
peter0x44.github.io
|
|
| | | | | Cross compilation is a common task during development, but different compilers and programming languages handle it in their own ways, and I wanted to write about the various flavors of trade-offs and design decisions that you will find across different tooling. I feel like I have absorbed a lot of information about how cross compilation works across different targets, tools and languages, so I figured it was time to condense my knowledge into a blog post. This is not a tutorial, but it still contains practically applicable knowledge. I don't claim to get every detail correct, merely explaining how things work to my understanding. | |
| | | | |
paul.totterman.name
|
|
| | | | | Like many other developers, I have to work with computers with different processor architectures. For me it's amd64 (x86_64) on the laptop and arm64 (aarch64) on the server. For some it may be the other way around. Fortunately I mostly write Go, which makes cross-compilation quite easy. Docker adds some extra steps, but is very nice for deploying software. | |
| | | | |
golangcookbook.com
|
|
| | | | | ||
| | | | |
pierre-couy.dev
|
|
| | | A tutorial featuring two examples showing how you can increase your privacy using nginx to proxy third-party services. | ||