[MacPorts] #60987: meson: not finding pkg-config when building universal when using cross-files

MacPorts noreply at macports.org
Wed Aug 12 14:55:44 UTC 2020


#60987: meson: not finding pkg-config when building universal when using cross-
files
-----------------------------+--------------------
  Reporter:  kencu           |      Owner:  (none)
      Type:  defect          |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:
Resolution:                  |   Keywords:
      Port:  meson graphene  |
-----------------------------+--------------------

Comment (by Gcenx):

 Replying to [comment:16 ryandesign]:
 > I don't think there is any other situation where MacPorts base modifies
 the environment in response to a dependency being added or removed, so
 this would be an entirely new feature to add to MacPorts base, and I'm not
 convinced it's necessary or the correct solution, given that MacPorts has
 survived for 18 years without it.

 You have a point, under normal conditions this won’t be needed.

 Replying to [comment:16 ryandesign]:
 > If meson uniquely among all build systems needs to be told where pkg-
 config can be found, then the meson portgroup can do that.

 The reason meson is now requiring to know where pkg-config/cmake/ect is
 due to it being used as a cross compiler not as a native compiler when
 building +universal, I’d guess that will be expanded later to cover all
 compilations.

 Replying to [comment:16 ryandesign]:
 > I would just urge extreme caution with making such changes. MacPorts
 provides ports not just for its own use but also for users to use, and
 users expect programs to work the way their developers intended. It's not
 our place to change how the tool works just to suit the purposes of
 MacPorts builds.

 I don’t disagree with the stance, patching meson could potentially cause
 an issue when used for real cross compilation of the crossfile doesn’t
 provide its own wrappers for pkg-config/cmake/ect for the intended target.

 Replying to [comment:16 ryandesign]:
 > It is reasonable to open a discussion with the developers of meson,
 explain why this setting is causing us problems, and ask if there is any
 recommended way for us to override the default when doing MacPorts builds
 (it seems likely to me that there would be such a way), or maybe even if
 they want to change the default.

 There stance has been to use the cross files (check DevKitPro as an
 example), however reaching out to them for a possible way to make use of
 {{{allow_default_for_cross=True}}} or similar as an environment variable
 would be more than ideal as the meson portgroup could just set this and
 then not need to worry about listing all possible binaries within the
 crossfile macports uses & also won’t affect an end users crossfiles in
 anyway.

-- 
Ticket URL: <https://trac.macports.org/ticket/60987#comment:18>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list