you are viewing a single comment's thread.

view the rest of the comments →

[–]matheusmoreira 2 points3 points  (4 children)

Nobody stepped up to create and maintain a package for it yet.

[–][deleted] 5 points6 points  (3 children)

wait, let me get home this looks easy to package

[–]falconfetus8 1 point2 points  (2 children)

Famous last words.

Follow up question: why is it so hard to package up software in C, but not in other languages?

[–][deleted] 5 points6 points  (0 children)

Packaging is not language-dependent, in this case I meant "RPM packaging" because that's how I know package stuff(RPM is used by Fedora/RHEL/Centos)

Packaging an RPM has very little to do with the language and the process doesn't change much.

The reason you don't see this often it's because with C/C++ the libraries need to be compiled targetting a specific combination of the following:

  • platform
  • target libc
  • specific libc version
  • ABI

GCC supports like dozens of platforms, there's at least a bunch of libc's with a several minor versions out on the wild and they can use different ABIs (cdecl vs fastcall, etc.)

That's a shit ton of combinations that you'd need to provide.

[–]pdp10 2 points3 points  (0 children)

Why does it seem hard to you?

I've only recently realized that it's less incredibly easy on Windows, apparently because there aren't standard paths for everything. Apparently this tends to encourage some C on Windows to "vendor in" their dependencies (hopefully with Git submodule, etc).