Requesting MacOSX10.13.SDK from XCode9.4.1.app #1

Closed
opened 2021-11-02 16:50:53 -05:00 by Gcenx · 5 comments
Gcenx commented 2021-11-02 16:50:53 -05:00 (Migrated from github.com)

This is the final available SDK that supports 32Bit it would be nice to have a prepackaged version available.

This is the final available SDK that supports 32Bit it would be nice to have a prepackaged version available.
joseluisq commented 2021-11-02 17:22:59 -05:00 (Migrated from github.com)

Sure, I'll see if I can get hold of the SDK for packaging it.

Sure, I'll see if I can get hold of the SDK for packaging it.
Gcenx commented 2021-11-02 17:47:21 -05:00 (Migrated from github.com)

I’d assumed you were downloading the relevant version of Xcode and running the script to package up the SDK.

Manually packing the SDKs found on GitHub won’t include the relevant C++ headers nor the man pages (and some other items), those are only found within the relevant Xcode.app

I’d assumed you were downloading the relevant version of Xcode and running the script to package up the SDK. Manually packing the SDKs found on GitHub won’t include the relevant C++ headers nor the man pages (and some other items), those are only found within the relevant Xcode.app
joseluisq commented 2021-11-02 18:24:09 -05:00 (Migrated from github.com)

I’d assumed you were downloading the relevant version of Xcode and running the script to package up the SDK.

Maybe I was misunderstood with "get the SDK". I meant xcode.
But yeah the method here is essentially the proper xcode download + packaging with the osxcross script.

Anyway what I meant was that since I have not a Mac at hand (I use someone else Mac) as soon as I can I could try to package it.

Manually packing the SDKs found on GitHub won’t include the relevant C++ headers nor the man pages (and some other items), those are only found within the relevant Xcode.app

Yeah, I think you mean those ones like phracker/MacOSX-SDKs, right? because the script used here looks at C++ headers and man pages. Isn't?

> I’d assumed you were downloading the relevant version of Xcode and running the script to package up the SDK. Maybe I was misunderstood with "get the SDK". I meant xcode. But yeah the method here is essentially _the proper xcode download + packaging with the osxcross script_. Anyway what I meant was that since I have not a Mac at hand (I use someone else Mac) as soon as I can I could try to package it. > Manually packing the SDKs found on GitHub won’t include the relevant C++ headers nor the man pages (and some other items), those are only found within the relevant Xcode.app Yeah, I think you mean those ones like `phracker/MacOSX-SDKs`, right? because [the script used here](https://github.com/tpoechtrager/osxcross/blob/master/tools/gen_sdk_package.sh#L183-L193) looks at C++ headers and man pages. Isn't?
Gcenx commented 2021-11-02 19:12:28 -05:00 (Migrated from github.com)

Maybe I was misunderstood with "get the SDK". I meant xcode. But yeah the method here is essentially the proper xcode download + packaging with the osxcross script.

Yeah that’s what I thought due to the mention of SDK, doing that produces useless results.

Anyway what I meant was that since I have not a Mac at hand (I use someone else Mac) as soon as I can I could try to package it.

Ah ok that makes sense, the version that contains the final build of the SDK is Xcode 9.4.1.

Yeah, I think you mean those ones like phracker/MacOSX-SDKs, right? because the script used here looks at C++ headers and man pages. Isn't?

That’s correct Xcode itself contains additional files, on macOS the alternative SDKs would work as the missing files are included within Xcode but when using osxcross those are missing.

> Maybe I was misunderstood with "get the SDK". I meant xcode. But yeah the method here is essentially _the proper xcode download + packaging with the osxcross script_. Yeah that’s what I thought due to the mention of SDK, doing that produces useless results. > Anyway what I meant was that since I have not a Mac at hand (I use someone else Mac) as soon as I can I could try to package it. Ah ok that makes sense, the version that contains the final build of the SDK is Xcode 9.4.1. > Yeah, I think you mean those ones like `phracker/MacOSX-SDKs`, right? because [the script used here](https://github.com/tpoechtrager/osxcross/blob/master/tools/gen_sdk_package.sh#L183-L193) looks at C++ headers and man pages. Isn't? That’s correct Xcode itself contains additional files, on macOS the alternative SDKs would work as the missing files are included within Xcode but when using osxcross those are missing.
joseluisq commented 2021-11-03 07:24:19 -05:00 (Migrated from github.com)

It has taken some time to download, convert the Xcode.app into a Xcode.dmg because looks like they are only providing .xip files (Xcode_9.4.1.xip).

$ ./tools/gen_sdk_package.sh
found Xcode: /Volumes/Xcode/Xcode.app
packaging MacOSX10.13 SDK (this may take several minutes) ...

-rw-r--r--   1 jq  staff    34M Nov  3 13:00 MacOSX10.13.sdk.tar.xz

But anyway here it is 10.13.
Feel free to give it a test.

It has taken some time to download, convert the `Xcode.app` into a `Xcode.dmg` because looks like they are only providing `.xip` files (`Xcode_9.4.1.xip`). ``` $ ./tools/gen_sdk_package.sh found Xcode: /Volumes/Xcode/Xcode.app packaging MacOSX10.13 SDK (this may take several minutes) ... -rw-r--r-- 1 jq staff 34M Nov 3 13:00 MacOSX10.13.sdk.tar.xz ``` But anyway here it is [10.13](https://github.com/joseluisq/macosx-sdks/releases/tag/10.13). Feel free to give it a test.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
miles/macosx-sdks#1
No description provided.