> The target selection configuration flag for Windows AArch64 should be added
> to the build documentation for improved discoverability and completeness.
Saint Wesonga has updated the pull request incrementally with one additional
commit since the last revision:
Simplify documentation
Co
On Tue, 15 Apr 2025 19:35:24 GMT, Saint Wesonga wrote:
>> The target selection configuration flag for Windows AArch64 should be added
>> to the build documentation for improved discoverability and completeness.
>
> Saint Wesonga has updated the pull request incrementally with two additional
> c
On Tue, 15 Apr 2025 19:35:24 GMT, Saint Wesonga wrote:
>> The target selection configuration flag for Windows AArch64 should be added
>> to the build documentation for improved discoverability and completeness.
>
> Saint Wesonga has updated the pull request incrementally with two additional
> c
> The target selection configuration flag for Windows AArch64 should be added
> to the build documentation for improved discoverability and completeness.
Saint Wesonga has updated the pull request incrementally with two additional
commits since the last revision:
- Add Visual Studio Build Tool
On Fri, 4 Apr 2025 14:28:00 GMT, Magnus Ihse Bursie wrote:
> It might still make sense to document that to cross-compile to aarch64, the
> flag `--openjdk-target=aarch64-unknown-cygwin` should be used -- that is in
> no way obvious or trivial to figure out.
ok, I'll leave the cross-compilation
On Wed, 26 Mar 2025 22:38:40 GMT, Saint Wesonga wrote:
> The target selection configuration flag for Windows AArch64 should be added
> to the build documentation for improved discoverability and completeness.
Wait a minute. I re-read the discussion a bit more carefully, and let my brain
re-pro
> The target selection configuration flag for Windows AArch64 should be added
> to the build documentation for improved discoverability and completeness.
Saint Wesonga has updated the pull request incrementally with one additional
commit since the last revision:
Clarify that instructions are
On Mon, 31 Mar 2025 18:11:27 GMT, Saint Wesonga wrote:
>> The target selection configuration flag for Windows AArch64 should be added
>> to the build documentation for improved discoverability and completeness.
>
> Saint Wesonga has updated the pull request incrementally with one additional
> c
On Mon, 31 Mar 2025 18:11:27 GMT, Saint Wesonga wrote:
>> The target selection configuration flag for Windows AArch64 should be added
>> to the build documentation for improved discoverability and completeness.
>
> Saint Wesonga has updated the pull request incrementally with one additional
> c
On Mon, 31 Mar 2025 18:11:27 GMT, Saint Wesonga wrote:
>> The target selection configuration flag for Windows AArch64 should be added
>> to the build documentation for improved discoverability and completeness.
>
> Saint Wesonga has updated the pull request incrementally with one additional
> c
On Mon, 31 Mar 2025 13:16:34 GMT, Erik Joelsson wrote:
> > Wait a minute. I re-read the discussion a bit more carefully, and let my
> > brain re-process what I said above...
> > Is the goal here to document how you properly do cross-compilation for
> > windows/aarch64 on windows/x64? If so, I t
> The target selection configuration flag for Windows AArch64 should be added
> to the build documentation for improved discoverability and completeness.
Saint Wesonga has updated the pull request incrementally with one additional
commit since the last revision:
Add instructions for a native
On Mon, 31 Mar 2025 14:44:23 GMT, Saint Wesonga wrote:
> Upon closer inspection, the --build option results in a native build (per the
> build system) but the ARM64 C++ compiler binary (cl.exe) is actually an x64
> binary, so the compiler is running in emulated mode despite the build system
>
On Mon, 31 Mar 2025 15:00:08 GMT, Saint Wesonga wrote:
> > > Wait, are you saying you can get a native build to work by setting
> > > --build=aarch64-pc-cygwin? If so, then that's a better instruction IMO.
> >
> >
> > No, it's not. If we could block the `--build` flag, we would. This is the
>
On Mon, 31 Mar 2025 10:14:54 GMT, Magnus Ihse Bursie wrote:
> > Wait, are you saying you can get a native build to work by setting
> > --build=aarch64-pc-cygwin? If so, then that's a better instruction IMO.
>
> No, it's not. If we could block the `--build` flag, we would. This is the
> built-i
On Mon, 31 Mar 2025 14:27:19 GMT, Erik Joelsson wrote:
> > But is the problem that we just fails to detect the _build_ platform, and
> > thus generates build tools for x64, instead of aarch64, which makes the
> > build fail? (Also, why doesn't the rosetta-equivalent kick in in that case?)
> > O
On Wed, 26 Mar 2025 22:38:40 GMT, Saint Wesonga wrote:
> The target selection configuration flag for Windows AArch64 should be added
> to the build documentation for improved discoverability and completeness.
> But is the problem that we just fails to detect the _build_ platform, and
> thus ge
On Mon, 31 Mar 2025 12:31:10 GMT, Magnus Ihse Bursie wrote:
> Wait a minute. I re-read the discussion a bit more carefully, and let my
> brain re-process what I said above...
>
> Is the goal here to document how you properly do cross-compilation for
> windows/aarch64 on windows/x64? If so, I t
On Wed, 26 Mar 2025 22:38:40 GMT, Saint Wesonga wrote:
> The target selection configuration flag for Windows AArch64 should be added
> to the build documentation for improved discoverability and completeness.
But is the problem that we just fails to detect the *build* platform, and thus
genera
On Thu, 27 Mar 2025 19:38:28 GMT, Erik Joelsson wrote:
> Wait, are you saying you can get a native build to work by setting
> --build=aarch64-pc-cygwin? If so, then that's a better instruction IMO.
No, it's not. If we could block the `--build` flag, we would. This is the
built-in autoconf tar
On Thu, 27 Mar 2025 18:32:20 GMT, Saint Wesonga wrote:
> I don't think `--build=aarch64-pc-cygwin` is equivalent to
> `--openjdk-target=aarch64-unknown-cygwin`. The build experts can clarify this
> but my understanding is that `--openjdk-target` automatically sets the --host
> and --target opt
On Wed, 26 Mar 2025 22:38:40 GMT, Saint Wesonga wrote:
> The target selection configuration flag for Windows AArch64 should be added
> to the build documentation for improved discoverability and completeness.
@swesonga
Your change (at version c15306a8213b48e369c2b40648a4fd1af2fe2dea) is now re
On Thu, 27 Mar 2025 11:37:29 GMT, Matthias Baesken wrote:
> Thanks for documenting it ! My colleague used instead
> '--build=aarch64-pc-cygwin' , is this equivalent ?
I don't think `--build=aarch64-pc-cygwin` is equivalent to
`--openjdk-target=aarch64-unknown-cygwin`. The build experts can cla
On Wed, 26 Mar 2025 22:38:40 GMT, Saint Wesonga wrote:
> The target selection configuration flag for Windows AArch64 should be added
> to the build documentation for improved discoverability and completeness.
I think this is fine for now, but ideally we should make configure understand
that th
On Wed, 26 Mar 2025 22:38:40 GMT, Saint Wesonga wrote:
> The target selection configuration flag for Windows AArch64 should be added
> to the build documentation for improved discoverability and completeness.
Thanks for documenting it !
My colleague used instead '--build=aarch64-pc-cygwin' ,
25 matches
Mail list logo
