Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device.
Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Of the applications that I know that could compile with Qt 6 but won't on macOS because they require .pc files, gnuplot and octave are two examples.
On macOS, I believe the includes are the same as on every other target, and frameworks need to use -F and -framework options. I don't know enough of cmake and the complex Qt build system to provide a patch, but I can help in testing.
Alexandru Croitor
July 31, 2023 at 11:36 PM
Nobody did the work. There are extra difficulties to handle there, like frameworks.
F' x
July 31, 2023 at 11:12 PM
On macOS, there are no .pc files installed by a Qt build from source. Is there a reason for that? It would be interesting to have them.
Be
July 26, 2022 at 1:23 PM
I stumbled upon Qt6 not providing pkgconfig files for static builds and found this bug. @Martin Reboredo, I think listing library file paths in the pkgconfig file for static builds could be okay. It is unusual to list library file paths rather than the typical `-L/path/to/dir -llibrary name` in pkgconfig files, but Qt5's pkgconfig files do this for static builds.
I am working on linking to Qt with Cargo and pkgconfig files are needed for that. I am using Qt from vcpkg on macOS and Windows, which defaults to static linking on macOS.
Alexandru Croitor
March 14, 2022 at 11:16 PM
That would be my intention, but the change has not been tested yet (to ensure it doesn't break anything) with all qt repos in our CI. This due to CI load though, not the change itself.
Qt 5 when built with qmake generates .pc files for projects that wish to consume dependencies using pkg-config files.
We should evaluate whether we should do the same, and if yes, provide them with the CMake built Qt 6 packages.