3 ms·

> run ./configure > realize i’m missing a dependency If only there was like, a tool, to help you manage compile-time dependencies. I wish there was a `yarn` e

> run ./configure > realize i’m missing a dependency If only there was like, a tool, to help you manage compile-time dependencies. I wish there was a `yarn` equivalent for C projects.

rhn_mk1 7y ago
I find pkgconfig + dnf install pkgconfig(foo) useful
jkbbwr 7y ago
This problem is 1000% harder than you think it is, and everyone has a different idea on how to solve it.
- MuffinFlavored 7y ago
  Sure, but like... `package.json` as a source of truth for dependencies (package names + semver criteria to match) followed by abstracting fetch + build away through one command `yarn install` Those two concepts will always remain the same despite the underlying workings, no?
  - progval 7y ago
    That's what distributions do. For example in Debian, the lists of build and run-time dependencies are in ./debian/control
deleted 7y ago
[deleted]
pjc50 7y ago
In some ways the entire concept of "Linux distribution" developed to address this. Certainly if you stay within a distro ecosystem it will have tools to do this for you in both Debian and Redhat.
- maple3142 7y ago
  But doesn't this make compiling program on systems without these tools hard? For example, it is not easy to compile those programs on Windows without WSL or Cygwin.
  - pjc50 7y ago
    Well, it doesn't make it easier. I suppose you could try building a set of RPM packages for the Windows platform, which is basically what Cygwin is. If you're saying "wouldn't it be great if C the language came with an integrated package manager that worked the same on all platforms and was available everywhere", then yes, that would be great, and I too would like a pony. I just think the ecosystem is way too fragmented to ever achieve that. Doubly so if you have to start thinking about cross-compilers and the long tail of little embedded targets.
eitland 7y ago
Working with other languages was how I realized how brilliant the combo of Maven and Java was ;-) (PS: today Yarn and Nuget does some of this for the Node/JS/etc and .Net ecosystem but back when Maven arrived those weren't even planned.)
gravypod 7y ago
I wish we just collectively stuck to a single language agnostic build systems like buck, pants, or bazel and distributed everything with BUILD files.
camgunz 7y ago
Haha, I actually feel exactly the opposite! I wish JS, Ruby, Python, etc. deferred to OS-specific package management. Mandatory xkcd reference, etc.

> run ./configure > realize i’m missing a dependency If only there was like, a tool, to help you manage compile-time dependencies. I wish there was a `yarn` equivalent for C projects.

rhn_mk1 7y ago

I find pkgconfig + dnf install pkgconfig(foo) useful

jkbbwr 7y ago

This problem is 1000% harder than you think it is, and everyone has a different idea on how to solve it.

MuffinFlavored 7y ago
Sure, but like... `package.json` as a source of truth for dependencies (package names + semver criteria to match) followed by abstracting fetch + build away through one command `yarn install` Those two concepts will always remain the same despite the underlying workings, no?
- progval 7y ago
  That's what distributions do. For example in Debian, the lists of build and run-time dependencies are in ./debian/control

deleted 7y ago

[deleted]

pjc50 7y ago

In some ways the entire concept of "Linux distribution" developed to address this. Certainly if you stay within a distro ecosystem it will have tools to do this for you in both Debian and Redhat.

maple3142 7y ago
But doesn't this make compiling program on systems without these tools hard? For example, it is not easy to compile those programs on Windows without WSL or Cygwin.
- pjc50 7y ago
  Well, it doesn't make it easier. I suppose you could try building a set of RPM packages for the Windows platform, which is basically what Cygwin is. If you're saying "wouldn't it be great if C the language came with an integrated package manager that worked the same on all platforms and was available everywhere", then yes, that would be great, and I too would like a pony. I just think the ecosystem is way too fragmented to ever achieve that. Doubly so if you have to start thinking about cross-compilers and the long tail of little embedded targets.

eitland 7y ago

Working with other languages was how I realized how brilliant the combo of Maven and Java was ;-) (PS: today Yarn and Nuget does some of this for the Node/JS/etc and .Net ecosystem but back when Maven arrived those weren't even planned.)

gravypod 7y ago

I wish we just collectively stuck to a single language agnostic build systems like buck, pants, or bazel and distributed everything with BUILD files.

camgunz 7y ago

Haha, I actually feel exactly the opposite! I wish JS, Ruby, Python, etc. deferred to OS-specific package management. Mandatory xkcd reference, etc.