Explore >> Select a destination
|
You are here 
|
www.tangramvision.com | ||
| | | | |
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. | |
| | | | |
maxfierke.com
|
|
| | | | | ||
| | | | |
ashvardanian.com
|
|
| | | | | Experienced devs may want to skip the intro or jump immediately to the conclusions. The backbone of many foundational software systems - from compilers and interpreters to math libraries, operating systems, and database management systems - is often implemented in C and C++. These systems frequently offer Software Development Kits (SDKs) for high-level languages like Python, JavaScript, GoLang, C#, Java, and Rust, enabling broader accessibility. But there is a catch. | |
| | | | |
galowicz.de
|
|
| | | Most big C++ projects lack a clear structure:They consist of multiple modules, but it is not as easy to create individuallybuildable, portable, testable, and reusable libraries from them, as it is withprojects written in Rust, Go, Haskell, etc.In this article, I propose a C++ project structure using CMake that makes iteasy to have incremental monorepo builds and a nice modular structure at thesame time. | ||
