Stay up-to-date with everything C++!
Content directly fetched from the subreddit just for you.
Join our group for discussions : @programminginc
Powered by : @r_channels
Post #25461
14
The problem with targeting Linux
Linux unlike MacOS and Windows doesn't have a standardised SDK. This forces devs to either natively compile there or create SDK/sysroot ourselves.
​
This creates some issues, firstly everyone targets different sets of packages for shared linking, this causes glibc version mismatches and similar issues.
​
In the end, why are we dealing with this, why can't Debian and Ubuntu Devs just collaborate to release a tarball for arm64 and x64 desktop. We could just download it and set the flags and everything works.
​
But currently we have to create a sysroot via docker, weird system packages with Debian etc. None of them are really ideal.
​
The rest of the Devs who target mini-pc's or try to run Linux on milkv-duos can build their own sysroot from scratch, while we can just move to actual work.
​
https://redd.it/1ub4s64
@r_cpp
Linux unlike MacOS and Windows doesn't have a standardised SDK. This forces devs to either natively compile there or create SDK/sysroot ourselves.
​
This creates some issues, firstly everyone targets different sets of packages for shared linking, this causes glibc version mismatches and similar issues.
​
In the end, why are we dealing with this, why can't Debian and Ubuntu Devs just collaborate to release a tarball for arm64 and x64 desktop. We could just download it and set the flags and everything works.
​
But currently we have to create a sysroot via docker, weird system packages with Debian etc. None of them are really ideal.
​
The rest of the Devs who target mini-pc's or try to run Linux on milkv-duos can build their own sysroot from scratch, while we can just move to actual work.
​
https://redd.it/1ub4s64
@r_cpp