[Octave-bug-tracker] [bug #55282] QT_CPPFLAGS and QT_LDFLAGS command-line / environment vars ignored by configure

[Andrew Janke]

Follow-up Comment #21, bug #55282 (project octave):

> Andrew, please see Mike's suggestion below. Can you report the problem with
pkg-config back to Homebrew?

I'll look in to it. I don't quite understand the issue well enough to make a
bug report yet; playing around with it tonight.

> Thus "# include <module/include.h>" works on linux, but cannot work on macOS
unless the linux directory structure is created using symbolic links. The Qt
from Homebrew is setup this way (so -I/usr/opt/qt/include could be added to
each module's pc-file). However, I don't know if this directory structure is
Homebrew's creation or part of Qt. If the latter, a bug report could be
filed.

This is Homebrew's creation. It's done as part of the qt formula's install
script. A vanilla Qt install will not have them.

https://github.com/Homebrew/homebrew-core/blob/0de5e99130bb5462af029d0d5d238b7a9b09e817/Formula/qt.rb#L52-L57


    # The pkg-config files installed suggest that headers can be found in the
    # `include` directory. Make this so by creating symlinks from `include`
to
    # the Frameworks' Headers folders.
    Pathname.glob("#{lib}/*.framework/Headers") do |path|
      include.install_symlink path => path.parent.basename(".framework")
    end


That is, Homebrew does not change Qt's pkgconfig files, but it does alter the
layout of the Qt installation to reflect what its pkgconfig files are saying.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55282>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/