[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: macOS 64-bit
From: |
Jahrme Risner |
Subject: |
Re: macOS 64-bit |
Date: |
Thu, 16 May 2019 22:58:01 +0000 |
On Thu, May 16, 2019 at 15:39, David Kastrup <address@hidden> wrote
> You would not be allowed to execute GUB on non-MacOSX hardware if using
> Xcode were an integral part of its operation, and this kind of
> restriction is not allowed by the GPLv3.
The way I had been approaching an addition of 64-bit Darwin to GUB was that,
due to the Xcode restrictions, on non-Apple hardware GUB would compile all
non-Darwin targets and simply ignore requests for Darwin targets, perhaps with
a warning. In order to produce a Darwin release, someone would need to install
GUB on a Mac and run the Darwin build from there. This would mean that Darwin
binaries might lag behind other architectures until someone with a Mac could
get around to producing a build.
To my understanding this is no different than an application *providing* GPU
acceleration capabilities but not requiring it; it does not mean that someone
without a GPU cannot run the software, just that they are not using features
irrelevant to their hardware. We would be *providing* the option to build
Darwin *if* on a Mac, not requiring a Mac for GUB to run.
If this is still too much of an ask then perhaps I am missing some finer point.
- Re: macOS 64-bit, marnen, 2019/05/16
- Re: macOS 64-bit, David Kastrup, 2019/05/16
- Re: macOS 64-bit, Marnen Laibow-Koser, 2019/05/16
- Re: macOS 64-bit, Marnen Laibow-Koser, 2019/05/16
- Re: macOS 64-bit, David Kastrup, 2019/05/16
- Re: macOS 64-bit, Marnen Laibow-Koser, 2019/05/16
- Re: macOS 64-bit, David Kastrup, 2019/05/16
- Re: macOS 64-bit, Marnen Laibow-Koser, 2019/05/16
- Re: macOS 64-bit, Marnen Laibow-Koser, 2019/05/16
- Re: macOS 64-bit,
Jahrme Risner <=
- Re: macOS 64-bit, Hans Åberg, 2019/05/16
Re: macOS 64-bit, Jahrme Risner, 2019/05/16
Re: macOS 64-bit, Marnen Laibow-Koser, 2019/05/21