Building Chromium #24
Replies: 6 comments 34 replies
-
Oh, I didn't know about that warning...which Xcode are you using for the build? I'm still not familiar with highly complicated Chromium's build system, but full text search shows Or, you can specify 10.9 for build target by changing |
Beta Was this translation helpful? Give feedback.
-
Hi! There is an any chances to build chromium legacy for Mac OS X 10.6.8 Snow Leopard? |
Beta Was this translation helpful? Give feedback.
-
Fwiw, MacPorts has a working libc++.dylib for 10.6 which it uses extensively. It’s much newer than 10.7!
Sent from my phone, please excuse typos.
… On Oct 15, 2021, at 5:18 PM, blueboxd ***@***.***> wrote:
Yes, you can complete the build process for 10.6 with some workarounds (modifications to source and macOS SDK).
But resulted binary is not usable on 10.6 because of many unavailable APIs compared to 10.7.
Maybe some of these APIs are not used, but I think many of these are essential.
And, libc++ is not available on 10.6, so you also need workarounds for that.
(simply copying libc++.dylib to 10.6 not working)
FYI, the list of unavailable APIs is attached.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
Beta Was this translation helpful? Give feedback.
-
Hmm. That is indeed quite a list of missing APIs... I think the toolchain and libc++ needs are met by MacPorts tooling -- but the SDK and System roots just might not be up to the task. It would take a bit of actually digging to see how many of these can be worked around, and it looks like no small task! I have not as yet tried to dive in on SnowLeopard as yet. It would sure be nice to have, but might be a touch out of reach... Really really good job getting this going on 10.7+ by the way! Much appreciated! |
Beta Was this translation helpful? Give feedback.
-
@blueboxd Has the build process changed at all since the summer? I had to remove Unfortunately, I then began receiving errors about missing header files. E.g.:
VM is running macOS 11.0.1 and Xcode 12.5.1. I've tried using both MacOSX11.3.sdk and MacOSX12.1.sdk. |
Beta Was this translation helpful? Give feedback.
-
I've documented what I had to do to build Chromium at the bottom of the wiki page. https://github.com/blueboxd/chromium-legacy/wiki/Building Eventually, this should probably be integrated into the main instructions, but I wanted someone (Bluebox) to confirm they were the right things to do! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I finally have a VM set up on a new enough version of macOS to build Chromium, so I'm trying to run Bluebox's build script.
It appears to have successfully downloaded all of the dependencies, but the build is failing. I think
ld
is angry that the deployment target is set to 10.7?I assume I need to turn off
-fatal_warnings
, but Chromium's build system is so complicated, I can't actually tell where to change that! Any pointers?Full Terminal output from the build script is attached. I'm sure this won't be the last roadblock, but one step at a time...
Saved Terminal Output 2021.07.30.txt
Beta Was this translation helpful? Give feedback.
All reactions