pkgconf VS cmake-init-clang-on-windows

this may only be effecting fedora 39 users, but how i resolved it was by going to pkg config repo where then i checked out version 2.0. then i compiled, and installed pkg-config manually. double checked that the version was now 2.0 up from 1.9.5. then went back into the cardano node repo and packages were found successfully during compilation. not sure what is up with pkg-config not working on version 1.9.5 but i'm glad it's over, and hopefully this helps anyone else out suffering from the same thing. may the force be with you all.

pkgconf 1.9 seems to be only an unstable release series that will result in the stable 2.0. See NEWS

Incidentally, there is already a fork in the form of the pkgconf project: https://github.com/pkgconf/pkgconf

Is the author the same person that talks about Inclusivity, and then posts screencaps of other people they are having disagreements with to twitter, for their followers to sneer at? [1]

Is this the same person who uses the departure of a developer as a reason to "fix" a community [2], when the mailmap of one of their projects shows they are referring to their own faked departure? [3]

This stuff doesn't make the Alpine Linux project look good. I totally see that its very rude to attack a person like this, but i think its abusive behavior and needs to be called out.

[1] https://twitter.com/ariadneconill/status/1445586541040979971

[2] https://ariadne.space/2021/08/08/on-the-topic-of-community-m...

[3] https://github.com/pkgconf/pkgconf/blob/master/.mailmap

Or LLVM Clang directly without a pseudo *nix environment: https://github.com/friendlyanon/cmake-init-clang-on-windows

While not embedded, but here is an example for compiling with LLVM Clang on Windows without needing vcvarsall.

I was informed that this is not the case. lld supports PE/COFF natively on Windows. You just need to provide some flags to use the MSVC .lib and include files to use Clang properly. Or use the vcvarsall, but that's stinky and I don't like having all that env stuff in my terminal all the time.

Regarding building, I'd advise staying as far away from Mingw, msys and Cygwin as possible. You can just use LLVM Clang without any issue on Windows. You can keep using vim with Clang tools as if you were on Linux still.

CMake, Clang and Conan work all the same on all operating systems. I don't know why you would like to force yourself into one kind of environment that might not suit your needs in other areas as well. On Windows, you can even use LLVM Clang without godawful hacks like mingw.

From a quick searching I found what it takes to compile a Windows executable on macOS, these flags could be very easily turned into a toolchain file and the situation would be similar on Linux as well.

cmake-init was just for a general project setup. One of the examples in fact shows what a toolchain file should look like.

You can also just use LLVM Clang on Windows. Still requires MSVC installed though, because of link.exe, system .libs and system headers.