[mu bug] Issues locating packages on Mac OS X

[md-zengo]

In order to install mu, using

meson build && ninja -C build

I had to
export PKG_CONFIG_PATH=/opt/homebrew/Cellar/gmime/3.2.14/lib/pkgconfig:/opt/homebrew/Cellar/xapian/1.4.24/lib/pkgconfig

Otherwise I would get an error:

Software:

    System Software Overview:

      System Version: macOS 14.2.1 (23C71)
      Kernel Version: Darwin 23.2.0
      Boot Volume: Macintosh HD
      Boot Mode: Normal
      Computer Name: Michael-David’s MacBook Air
      User Name: Michael-David Fiszer (mdf)
      Secure Virtual Memory: Enabled
      System Integrity Protection: Enabled
      Time since boot: 4 days, 8 minutes

Hardware:

    Hardware Overview:

      Model Name: MacBook Air
      Model Identifier: MacBookAir10,1
      Model Number: Z1280006CHB/A
      Chip: Apple M1
      Total Number of Cores: 8 (4 performance and 4 efficiency)
      Memory: 16 GB
      System Firmware Version: 10151.61.4
      OS Loader Version: 10151.61.4
      Serial Number (system): C02GN05TQ6LX
      Hardware UUID: 44D8A5C0-C872-542F-9176-8CAB8B868E9E
      Provisioning UDID: 00008103-000830CA1AF3001E
      Activation Lock Status: Enabled

[djcb]

Seems like its working as expected? I.e., mu can't possibly guess those locations unless you tell it (through that export).

[guibor]

I'm not an expert in mac packages but I never encounter these types of issues normally. I'm sure there's a way to solve it so that it's smooth for everyone that installed the right packages from homebrew (which is how I installed them).

If not, I would add information in the installation instructions to help.

Keep up the amazing work! I love mu4e!!

[djcb]

To make it work out-of-the-box, I guess the Homebrew folks need to update PKG_CONFIG_PATH. Perhaps they're already doing that? See e.g. https://github.com/orgs/Homebrew/discussions/2987

Anyway, there's not much mu can do here... so closing this. Thanks for your report.