#pkgconfig — Public Fediverse posts

#pkgconfig's rules about when it does or does not apply a sysroot base seem to be very inconsistent. I guess I'm going to have to look at the actual code to see why this may be. #crosscompiling #buildroot

#pkgconfig's rules about when it does or does not apply a sysroot base seem to be very inconsistent. I guess I'm going to have to look at the actual code to see why this may be. #crosscompiling #buildroot

#pkgconfig's rules about when it does or does not apply a sysroot base seem to be very inconsistent. I guess I'm going to have to look at the actual code to see why this may be. #crosscompiling #buildroot

#pkgconfig's rules about when it does or does not apply a sysroot base seem to be very inconsistent. I guess I'm going to have to look at the actual code to see why this may be. #crosscompiling #buildroot

#pkgconfig's rules about when it does or does not apply a sysroot base seem to be very inconsistent. I guess I'm going to have to look at the actual code to see why this may be. #crosscompiling #buildroot

Trying to compile my #opensource project with #visualstudio instead of #qtcreator on #linux

Why is the world under Windows to Linux so much different for #cmake ?

I spent too much time to find a solution for the non-existing #pkgconfig under this environment. Finally #mingw saved me and an adaptation of the path setting.

Trying to compile my #opensource project with #visualstudio instead of #qtcreator on #linux

Why is the world under Windows to Linux so much different for #cmake ?

I spent too much time to find a solution for the non-existing #pkgconfig under this environment. Finally #mingw saved me and an adaptation of the path setting.

Hot take after an afternoon un-fsck-ing a #CMake project: `*Config.cmake` files are so much harder to debug than `*.pc` #PKGConfig files, so not only are you trying to make sense of a Turing complete project definition but all the transitive dependencies that happen to use CMake too

I'm increasingly a #meson fan.

Hot take after an afternoon un-fsck-ing a #CMake project: `*Config.cmake` files are so much harder to debug than `*.pc` #PKGConfig files, so not only are you trying to make sense of a Turing complete project definition but all the transitive dependencies that happen to use CMake too

I'm increasingly a #meson fan.

Hot take after an afternoon un-fsck-ing a #CMake project: `*Config.cmake` files are so much harder to debug than `*.pc` #PKGConfig files, so not only are you trying to make sense of a Turing complete project definition but all the transitive dependencies that happen to use CMake too

I'm increasingly a #meson fan.

Hot take after an afternoon un-fsck-ing a #CMake project: `*Config.cmake` files are so much harder to debug than `*.pc` #PKGConfig files, so not only are you trying to make sense of a Turing complete project definition but all the transitive dependencies that happen to use CMake too

I'm increasingly a #meson fan.

Hot take after an afternoon un-fsck-ing a #CMake project: `*Config.cmake` files are so much harder to debug than `*.pc` #PKGConfig files, so not only are you trying to make sense of a Turing complete project definition but all the transitive dependencies that happen to use CMake too

I'm increasingly a #meson fan.

A trick for #compiling on #Fedora:

when the compilation fails on a missing package, you might see sth like:

"library scintilla-3 not found, tried pkgconfig"

With #dnf, it's easy to fix:

```
dnf install "pkgconfig(scintilla-3)"
```

and dnf will find the package by library name for you!

(And then compile again and again and find out that 20 other packages were missing...)

#coding #pkgconfig

A trick for #compiling on #Fedora:

when the compilation fails on a missing package, you might see sth like:

"library scintilla-3 not found, tried pkgconfig"

With #dnf, it's easy to fix:

```
dnf install "pkgconfig(scintilla-3)"
```

and dnf will find the package by library name for you!

(And then compile again and again and find out that 20 other packages were missing...)

#coding #pkgconfig

A trick for #compiling on #Fedora:

when the compilation fails on a missing package, you might see sth like:

"library scintilla-3 not found, tried pkgconfig"

With #dnf, it's easy to fix:

```
dnf install "pkgconfig(scintilla-3)"
```

and dnf will find the package by library name for you!

(And then compile again and again and find out that 20 other packages were missing...)

#coding #pkgconfig

A trick for #compiling on #Fedora:

when the compilation fails on a missing package, you might see sth like:

"library scintilla-3 not found, tried pkgconfig"

With #dnf, it's easy to fix:

```
dnf install "pkgconfig(scintilla-3)"
```

and dnf will find the package by library name for you!

(And then compile again and again and find out that 20 other packages were missing...)

#coding #pkgconfig

A trick for #compiling on #Fedora:

when the compilation fails on a missing package, you might see sth like:

"library scintilla-3 not found, tried pkgconfig"

With #dnf, it's easy to fix:

```
dnf install "pkgconfig(scintilla-3)"
```

and dnf will find the package by library name for you!

(And then compile again and again and find out that 20 other packages were missing...)

#coding #pkgconfig