public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Ali Sherief <ali@notatether•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Bitcoin Core on ARM (Windows)
Date: Thu, 21 Nov 2024 01:03:39 -0800 (PST)	[thread overview]
Message-ID: <e5b06aaa-1fe9-4c8f-a0ea-db10f8a7e48cn@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1156 bytes --]

Apparently, there are only ARM binaries for Linux but not for Windows.

Considering that Apple Silicon is basically ARM as well, that means ARM 
binaries are produced for all the major operating systems except for 
Windows.

What would the process of compiling Windows with the ARM toolchain look 
like? Do any of these methods have Arm64 support?

> On Linux, using the Mingw-w64 cross compiler tool chain.
> On Windows, using Windows Subsystem for Linux (WSL) and Mingw-w64.
> On Windows, using Microsoft Visual Studio. See build-windows-msvc.md.

These are from the Windows build guide by the way.

I suppose Visual Studio might support ARM, but perhaps there are some 
x86-specific assembly functions used inside the codebase which might make 
it difficult to build.

- Ali

-- 
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/e5b06aaa-1fe9-4c8f-a0ea-db10f8a7e48cn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1583 bytes --]

             reply	other threads:[~2024-11-21  9:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21  9:03 Ali Sherief [this message]
2024-11-21 23:57 ` [bitcoindev] " Antoine Riard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e5b06aaa-1fe9-4c8f-a0ea-db10f8a7e48cn@googlegroups.com \
    --to=ali@notatether$(echo .)com \
    --cc=bitcoindev@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox