Support M1 and Android x64 #5
Comments
|
Buildware is by the way not entirely complete as for Mac and iOS glsl_optimizer (libglcpp-library, libglsl-optimizer.a and libmesa.a) is missing. I've build these for Mac using https://github.com/aras-p/glsl-optimizer (and just change target in xcode to standard platforms; intel and apple silicon). |
|
The glsl-optimizer support cmake, maybe could be add to buildware also. |
|
Yes indeed! I've modified the build script to generate the library from https://github.com/cocos2d/glsl-optimizer. Tomorrow I'll clean the scripts, modify the distribution scripts and make sure these only can be build for iOS and OSX. From there the buildscripts should basically download and build everything (except perhaps luajit a I just cannot get those to work). |
|
Done. Last commit in my fork should now also generate glsl-optimizer libraries and add them to the release zip. Again I did not look at the Powershell scripts as I do not have a Windows computer or VM available for that. |
|
The glsl-optimizer only for mac/ios, so no needs to build windows for it. |
|
Seems we can't cross compile osx arm64(M1) through github actions: |
|
Apple M1 support is in github action roadmap, but not complete yet, refer to: github/roadmap#528 |
|
Hm.. what happens when you build the x86_64. Might be an error in the script (which runs for me but perhaps exactly opposite on a x86_64)?
Sent from Nine<http://www.9folders.com/>
…________________________________
From: 一线灵 ***@***.***>
Sent: Friday, August 12, 2022 16:04
To: axys1/buildware
Cc: pietpukkel; Author
Subject: Re: [axys1/buildware] Support M1 and Android x64 (Issue #5)
Seems we can't cross compile osx arm64(M1) through github actions:
[image]<https://user-images.githubusercontent.com/6977319/184369893-effb3482-ede2-4a61-b280-0342bca17a94.png>
―
Reply to this email directly, view it on GitHub<#5 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AADT3TT7YLI7O7OOVA5WWW3VYZKVZANCNFSM56IOROEQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Let us wait the latest action finished and dist again |
|
Yes, maybe script error for openssl: CONFIG_ALL_OPTIONS=darwin64-x86_64-cc no-tests no-comp no-async no-shared --prefix=/Users/runner/work/buildware/buildware/install_osx_arm64/openssl --openssldir=/Users/runner/work/buildware/buildware/install_osx_arm64/openssl |
|
I am checking. What architecture do you build on? Mac x64?
On 12 Aug 2022, at 16:20, 一线灵 ***@***.******@***.***>> wrote:
Yes, maybe script error for openssl:
CONFIG_ALL_OPTIONS=darwin64-x86_64-cc no-tests no-comp no-async no-shared --prefix=/Users/runner/work/buildware/buildware/install_osx_arm64/openssl --openssldir=/Users/runner/work/buildware/buildware/install_osx_arm64/openssl
—
Reply to this email directly, view it on GitHub<#5 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AADT3TVMS5AF2XZKSSUEGXTVYZMSJANCNFSM56IOROEQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Yes, the github action only provide macos x86_64 vm currently |
|
I learn new things everyday. I did not know these were build automatically in Git in VMs. That’s quite cool.
I think it was an error in buid1.sh. I’ve reversed the compilers and on my iMac Pro it now builds the M1 binaries. Sorry that I did not test that before.
On 12 Aug 2022, at 16:22, 一线灵 ***@***.******@***.***>> wrote:
Yes, the github action only provide macos x86_64 vm currently
—
Reply to this email directly, view it on GitHub<#5 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AADT3TSSM3BEWFPMMHBL5NLVYZM3PANCNFSM56IOROEQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
The logic check seems incorrect: |
|
No worries, I will fix it |
|
Just ran it again in my x64 Mac and my latest commit also fixes it. No need for an M1 runner 😉 |
|
Good job |
|
The openssl osx arm64 seems still failed: /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/machine/_types.h:34:2: error: architecture not supported |
|
Might be due to the MacOS version of the runner and the commandline tools. Catelina does not support arm64 (only Big Sur and up). The scripts run correctly on a MacOS 12.5 system (Monterey). If you want I can run them for you. |
|
MacOSX10.15.sdk is too "old". |
|
OK, I upgrade it, and works on github action: https://github.com/axys1/buildware/actions/runs/2849072550 |
|
Looks like it worked 👍 |
|
Yes. Needs to be reversed.
On 12 Aug 2022, at 16:34, 一线灵 ***@***.******@***.***>> wrote:
The logic check seems incorrect:
https://github.com/axys1/buildware/blob/main/1k/build1.sh#L78
—
Reply to this email directly, view it on GitHub<#5 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AADT3TXZX4W35OEQIKLYFJ3VYZOIVANCNFSM56IOROEQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I've updated the buildscripts in my fork of buildware: see https://github.com/pietpukkel/buildware
Buildscript now builds (on my Mac) Mac x64 and arm64 binaries and the distribution scripts make them to fat libraries. I've also added x64 libraries for Android (have not been able to test the results yet). Delete all files in buildsrc after every build.
The only issue that I have is in bulding libjitlua. Building seems to succeed for iOS/Mac but the resulting libs are most likely corrupted. Building for Android fails (for luajit). So these build steps need some TLC from someone with a bit more expertise than I have. I also see no test that actually uses this library.
Assuming the windows powershell scripts only generate the libraries for windows, i have not touched these (or looked at them).
The text was updated successfully, but these errors were encountered: