Splitting the definition and the active flags allows overriding the flags per package. So if a package does not build with option X, we can just disable it by not setting it in the makepkg.conf.
Ah, okay!
I thought about putting the current version of the flags.yaml into the package and read the yaml file with the shim. But true, makes more sense to read the makepkg.conf for flags.
W…
I guess reading the flags.yaml makes the most sense, to specify what the shim should do
If I add the required fields in the process, would your software ignore them?
Hey @anonfunc,
what's the new URL for this?
That could also work, sure. Now we just need to figure out how to 'install' the shim into the chroot copy before building.
I guess the best solution would be, to create a package for the shim…
Somehow this dropped at the back of my head, sorry for that.
So we still need this for the project, correct?
Please update your whole system in one go. Otherwise there may be a mismatch of library versions etc.
Partly updating your system is not supported by ArchLinux.
@anonfunc the cython package needs a .2 bump. Had 0.29.34-3.1 installed which is still linking to python 3.10. But if reinstalled I get the same version number but it's fixed.
Same…
Hey @anonfunc,
you can just ask pacman's database on that matter:
# pacman -Fy --regex '^usr/lib/python3.10'
@anonfunc the cython package needs a .2 bump. Had 0.29.34-3.1 installed which is still linking to python 3.10. But if reinstalled I get the same version number but it's fixed.
I think the shim should be static and just be fed by enviromental variables, like the regular CPP flags are as well.
So something like
CPP_FLAGS_GCC="-list -of -awsome -flags" CPP_FLAGS_CLA…
I feel like we should just try to build everything "as is" and have a look at the outcome.
As adding the multilib-repo to the system is a manual operation we can just flag it as experimental…
@anonfunc it doesn't affect wine at all, as wine will just not honer the system flags at all. :)
In this package the honering of system flags is patched in and they discovered why they are not…
Ah yeah, it's just a null flag in this instance anyway. I have removed it from my own configuration in the meantime. Will do the same here. Thanks for pointing this out!