Thanks, all. I got it working and pushed the new port.
-Aaron
On Fri, Jun 14, 2019 at 2:17 AM Joshua Root 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 a
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
>>>
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
Hi Ryan.
Thanks very much for the info. I managed to solve that problem by adapting the
code you pointed to.
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
> li
On Jun 13, 2019, at 02:01, Aaron Madlon-Kay wrote:
> I am working on a portfile for Sequel Pro (https://sequelpro.com/) and
> am reaching the limits of my understanding of the Xcode build system.
>
> Sequel Pro contains several framework subprojects, which get built
> along with the main target.
Hi all.
I am working on a portfile for Sequel Pro (https://sequelpro.com/) and
am reaching the limits of my understanding of the Xcode build system.
Sequel Pro contains several framework subprojects, which get built
along with the main target. If I build the project normally outside of
MacPorts t
