[MacPorts] #39221: Cannot deploy Qt applications with MacPorts port qt4-mac
MacPorts
noreply at macports.org
Mon May 27 08:03:31 PDT 2013
#39221: Cannot deploy Qt applications with MacPorts port qt4-mac
--------------------------------+-------------------------
Reporter: clemens.brunner@… | Owner: michaelld@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.1.3
Resolution: | Keywords:
Port: qt4-mac |
--------------------------------+-------------------------
Comment (by cal@…):
Replying to [comment:7 clemens.brunner@…]:
> Thanks, rebuilding tiff from source did get rid of this error message;
macdeployqt now works as expected.
We should really revbump tiff some time soon to fix this.
> I didn't know that manually setting the minimum target when building my
application had no effect. Do you think that's a MacPorts bug or expected
behavior?
That's intended. MacPorts is not affected by any environment variables you
have set by default. However, setting `macosx_deployment_target` doesn't
work with all ports correctly either, so chances are setting it might not
have any effect on `qt4-mac`.
> On a related note, it would be interesting to know why these situations
are not handled automatically by MacPorts; if some flags were updated,
shouldn't all my ports have been rebuilt to ensure consistent operation?
It's a trade-off; the question is whether we should force all users to
rebuild all ports because of a rather simple (and meaningless for most
users) change. Also, we currently don't have a facility in place to
trigger rebuilding all ports after a MacPorts update -- we only support
this for OS upgrades. Rev-bumping all ports isn't enough to fix this,
because some people might still use an older version of MacPorts.
--
Ticket URL: <https://trac.macports.org/ticket/39221#comment:8>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list