>compile C++ code on Windows 10
>binary executable works on Windows 3.1, Windows 95, Windows 98, (as long as it's x86) Windows XP, Windows 2000, Windows ME, Windows Vista, Windows 7, Windows 10 (x86 or x64)
>compile C++ code on Debian
>binary executable works on Debian-based distros and craps out on every other
>to maintain Linux binaries, get some lube ready and prepare to maintain binaries for 7-8 popular distro families
This is why Linux is a joke
Compile C++ code on Windows 10
Angel Phillips
Other urls found in this thread:
en.wikipedia.org
stackoverflow.com
twitter.com
Joseph Williams
Anyone can maintain those binaries, though. The person who wrote the software doesn't have to do it.
Gavin Martin
Unless you know, you're a one man team
Jaxon Lee
>compile C++ code on Windows 10
>binary executable works on Windows 3.1, Windows 95, Windows 98, (as long as it's x86) Windows XP, Windows 2000, Windows ME, Windows Vista, Windows 7, Windows 10 (x86 or x64)
this is not true
Bentley Parker
Anyone can take the source code and compile it for their distro of choice, then maintain that binary in their repos.
Juan Davis
>(x86 or x64)
There is no x64. You just mean 64-bit x86.
Xavier Turner
>trusting other people
Jeremiah Brown
>x86-64
>also known as x64, x86_64, AMD64 and Intel 64
en.wikipedia.org
Elijah Watson
if you're a one man team why do you care about binary compatibility with all the distros? just provide the source code and if someone from bumfuck OS wants to use it he can compile it himself
Colton White
What do you have to trust them with, really? As long as the source code is open anyone could do that with or without your permission.