Xcode INSTALL_PATH and framework paths
Aaron Madlon-Kay
aaron+macports at madlon-kay.com
Fri Jun 14 00:59:12 UTC 2019
Thanks, all. I got it working and pushed the new port.
-Aaron
On Fri, Jun 14, 2019 at 2:17 AM Joshua Root <jmr at macports.org> wrote:
>
> On 2019-6-14 02:28 , Ryan Schmidt wrote:
> >
> >
> > On Jun 13, 2019, at 09:37, Aaron Madlon-Kay wrote:
> >
> >> Now I have another issue: after installation the port is flagged as broken with the following message.
> >>
> >>> sequelpro-devel is using libstdc++ (this installation is configured to use libc++)
> >>
> >> As I understand it, the reason is that Sequel Pro contains a vendored binary framework that links to /usr/lib/libstdc++.6.dylib.
> >>
> >> What can I do about this?
> >>
> >> The portfile is here:
> >> https://github.com/amake/macports-ports/blob/sequelpro/aqua/sequelpro-devel/Portfile
> >
> > If the only files you install that link with a C++ library link with libstdc++, then you can specify that and the warning will go away:
> >
> > configure.cxx_stdlib libstdc++
> >
> > But if you're both installing a binary that links with libstdc++ *and* you want to compile other C++ software that links with the default C++ library, then we have no way to specify that.
>
> If that's the case, it will be detected as "mixed" and rev-upgrade will
> not try to rebuild.
>
> - Josh
More information about the macports-dev
mailing list