On Nov 9, 2019, at 19:49, Al Varnell wrote:
> On Nov 9, 2019, at 08:45, Ryan Schmidt wrote:
Have you tried installing the CLT ? That should provide a 10.14 SDK that
the latest MacPorts release will use.
>>>
>>> I thought CLT was installed with XCode.
>>
>> It was prior to Xcode
Sent from my iPad
On Nov 9, 2019, at 08:45, Ryan Schmidt wrote:
>>> Have you tried installing the CLT ? That should provide a 10.14 SDK that
>>> the latest MacPorts release will use.
>>
>> I thought CLT was installed with XCode.
>
> It was prior to Xcode 4. These days it is a separate
> Am 2019-11-09 um 17:45 schrieb Ryan Schmidt :
>
>>> That is a bad idea, pretending a 10.15 SDK is a 10.14 one could lead to
>>> unforeseen side effects. So this is not something we recommend anyone does.
>>
>> I’m a cowboy coder ;)
>
> Well, please revert the change so that it doesn't cause
On Nov 9, 2019, at 10:35, Henning Hraban Ramm wrote:
> Am 2019-11-09 um 15:07 schrieb Chris Jones:
>
>> On 9 Nov 2019, at 1:50 pm, Henning Hraban Ramm wrote:
>>
>>> Since I didn’t find a way to install a 10.14 SDK, I just made a symlink to
>>> the 10.15 SDK under the name of MacOSX10.14.sdk,
> Am 2019-11-09 um 15:07 schrieb Chris Jones :
>
>> On 9 Nov 2019, at 1:50 pm, Henning Hraban Ramm wrote:
>>
>> Hi,
>> I also had problems on Mojave, since at least cctools was expecting a
>> MacOSX10.14.sdk in
>>
> On 9 Nov 2019, at 1:50 pm, Henning Hraban Ramm wrote:
>
> Hi,
> I also had problems on Mojave, since at least cctools was expecting a
> MacOSX10.14.sdk in
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs;
> on Mojave there’s only the 10.15 SDK.
> I
Hi,
I also had problems on Mojave, since at least cctools was expecting a
MacOSX10.14.sdk in
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs;
on Mojave there’s only the 10.15 SDK.
I had XCode 10.something and updated yesterday to 11.latest; that needed some
Ehi Mojca,
Thanks for the message. :)
I managed to fix it. I got confused because recently I updated Xcode, but in
facts the problem was completely unrelated: I had a project header file named
“math.h”. :) Very noob mistake! Interestingly enough, this bug does not pop-out
on Linux (using
Dear Ruben,
This definitely looks like a bug in Xcode. I would suggest you to file
a bug report to Apple.
Can you please try to compile a simple hello world with just the
following contents
// test.cpp:
#include
int main() { return 0; }
and compile it with:
On 2019-10-13 02:06 , Ryan Schmidt wrote:
>
>
> On Oct 12, 2019, at 03:36, Chris Jones wrote:
>
>> On 12 Oct 2019, at 3:28 am, Ryan Schmidt wrote:
>>
>>> On Oct 11, 2019, at 09:57, Joshua Root wrote:
>>>
Xcode itself only contains a 10.15 SDK, but the Command Line Tools have
a 10.14
On Oct 12, 2019, at 03:36, Chris Jones wrote:
> On 12 Oct 2019, at 3:28 am, Ryan Schmidt wrote:
>
>> On Oct 11, 2019, at 09:57, Joshua Root wrote:
>>
>>> Xcode itself only contains a 10.15 SDK, but the Command Line Tools have
>>> a 10.14 one. You should be mostly fine with them installed,
> > But the CLT has the SDK in a different path than Xcode does, of course. And
> > if Xcode-based SDK paths got baked into various ports on our Xcode-10-using
> > Mojave build worker, then that will be a problem for any users that have
> > Xcode 11, whether or not they have the CLT.
>
> Does
> On 12 Oct 2019, at 3:28 am, Ryan Schmidt wrote:
>
> On Oct 11, 2019, at 09:57, Joshua Root wrote:
>
>> Xcode itself only contains a 10.15 SDK, but the Command Line Tools have
>> a 10.14 one. You should be mostly fine with them installed, though there
>> are some exceptions. Our
On Oct 11, 2019, at 09:57, Joshua Root wrote:
> Xcode itself only contains a 10.15 SDK, but the Command Line Tools have
> a 10.14 one. You should be mostly fine with them installed, though there
> are some exceptions. Our installation instructions have always said to
> install both Xcode and the
14 matches
Mail list logo
