You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's an existing PkgConfigFrontend in rock, it's just waiting to be adapted to handle the general case.
Note that llvm-config, sdl-config and all the im-better-than-you-config usually obey the same rules, aka 'util-name --cflags pkgname' or 'util-name --libs pkgname'.
However llvm-config itself has a little subtlety: it has --ldflags - we can't throw it by default because it'll trip up pkg-config and sdl-config (sigh) but we can allow CustomPackage to take additional arguments (3 and 4, respectively).
Anyway, I'm on it.
The text was updated successfully, but these errors were encountered:
pkg-config is the best thing that's happened to ooc since ACS.
Except it's not. Because some packages insist on having their own config tool, which sucks considerable balls (and ovaries).
For example, the ooc-llvm sample, right now, has a Makefile with the following C flags:
Which, needless to say, is less than ideal. We could alleviate the pain if we allowed this in .use files:
There's an existing PkgConfigFrontend in rock, it's just waiting to be adapted to handle the general case.
Note that llvm-config, sdl-config and all the im-better-than-you-config usually obey the same rules, aka 'util-name --cflags pkgname' or 'util-name --libs pkgname'.
However llvm-config itself has a little subtlety: it has --ldflags - we can't throw it by default because it'll trip up pkg-config and sdl-config (sigh) but we can allow CustomPackage to take additional arguments (3 and 4, respectively).
Anyway, I'm on it.
The text was updated successfully, but these errors were encountered: