Fix default ABI to allow using target-os instead of the default one - #340

Merged
olk merged 1 commit into
boostorg:developfrom
uilianries:fix/windows-android
Aug 14, 2026
Merged

Fix default ABI to allow using target-os instead of the default one#340
olk merged 1 commit into
boostorg:developfrom
uilianries:fix/windows-android

Conversation

@uilianries

@uilianriesuilianries commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Greeting!

After merging PR #334 and #335, when doing a few new validations with Boost 1.92.0-RC1 (se https://lists.boost.org/archives/list/boost@lists.boost.org/thread/U7DDTRXFCNGGZA5XZ5H6ZL2MUEFH5OLM/) I found a missing scenario when cross-building OS, mainly on Windows as host and another OS (e.g. Android) as target. The previous PRs fixed Context's ABI and binary-format defaults to derive from the deduced target (<target-os>/<architecture>) instead of the host platform, which is fine. However, the default_abi() still picks ms instead of the correct target ABI, even with target-os/architecture explicitly passed:

https://github.com/boostorg/context/blob/develop/boost-context-features.jam#L59

rule default_abi ( properties * )
{
local tmp = sysv ;
local arch = [ property.select <architecture> : $(properties) ] ;
if <target-os>windows in $(properties) { tmp = ms ; }
else if <target-os>cygwin in $(properties) { tmp = ms ; }
else if [ os.name ] = "NT" { tmp = ms ; }
else if [ os.name ] = "CYGWIN" { tmp = ms ; }
else if $(arch)
{
if <architecture>arm in $(properties) { tmp = aapcs ; }
else if <architecture>mips in $(properties)
{
if <address-model>64 in $(properties) { tmp = n64 ; }
else { tmp = o32 ; }
}
}

So, in case I try to cross-compile Boost Context from Windows to Android, even passing explicit target-os, abi, address-model, and architecture, I still have the following error during the setup:

error: No best alternative for /C:/Users/uilia/.conan2/p/b/boostbeb40f0cea2a9/b/src/libs/context/build/asm_sources with <abi>ms <address-model>64 <architecture>arm <asynch-exceptions>off <binary-format>elf <boost.beast.allow-deprecated>on <boost.beast.separate-compilation>on <boost.cobalt.executor>any_io_executor <boost.cobalt.pmr>std <boost.locale.iconv>off <boost.locale.icu>off <context-impl>fcontext <coverage>off <debug-symbols>none <exception-handling>on <extern-c-nothrow>off <inlining>none <known-warnings>hide <link>shared <optimization>none <os>NT <pch>on <preserve-test-targets>on <profiling>off <python-debugging>off <relevant>abi <relevant>address-model <relevant>architecture <relevant>binary-format <relevant>toolset <rtti>on <runtime-debugging>none <runtime-link>none <stdlib>native <strip>off <target-os>android <testing.execute>on <threadapi>pthread <threading>multi <toolset-clang:platform>linux <toolset-clang:version>18 <toolset>clang <variant>release <vectorize>off <visibility>hidden <warnings-as-errors>off <warnings>on <x-deduced-platform>arm_64
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>qcc
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>pe <threading>multi <toolset>msvc
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin
...

You can see my full build log with this error here: boost-1.92.0.rc1-windows-android-context.log

As default_abi is wired in as <conditional>@boost-context-features.default_abi, it overrides the explicit abi= on the command line too. So running b2 ... target-os=android architecture=arm abi=aapcs ... still fails the same way on a Windows host, and there's no command-line workaround.

This PR moves the [ os.name ] = "NT"/"CYGWIN" to mirror default_binary_format() structure. The host name is now consulted only when neither <target-os> nor <architecture> was part of the build request, so if a user passes it explicitly, the explicit one should prevail.

With this change, Context picks make_arm64_aapcs_elf_gas.S / jump_arm64_aapcs_elf_gas.S / ontop_arm64_aapcs_elf_gas.S when cross-building from Windows to Android/arm64, same as it already does correctly when cross-building from macOS or Linux.

I built locally, again Windows -> Android, and now I no longer have this error: boost-1.92.0.rc1-windows-android-context-patched.log

Environment

Host OS: Windows 10
Target OS: Android
Compiler: Android (13691557, based on r522817d) clang version 18.0.4 (https://android.googlesource.com/toolchain/llvm-project d8003a456d14a3deb8054cdaa529ffbf02d9b262) - Target:
Boost: 1.92.0-rc1

Steps to Reproduce

I used Conan initially, but I can reproduce when building from sources as well.

wget https://archives.boost.io/release/1.92.0/source/boost_1_92_0_rc1.zip
unzip boost_1_92_0_rc1.zip
cd boost_1_92_0/
bootstrap.bat
set "CXX=C:/Users/uilia/Development/android-ndk-r27d/toolchains/llvm/prebuilt/windows-x86_64/bin/aarch64-linux-android27-clang++.cmd"
b2 install target-os=android architecture=arm abi=aapcs binary-format=elf architecture=arm address-model=64 -d2 -q toolset=clang --layout=system

Note that as I'm cross-building, I have NDK 27d installed in my Windows, the official one from Android page. Android is just example, cross-building to Linux should result in the same.

Tell me if you need further validation or information about the case. Regards!

@uilianries
Fix when cross-building OS
54bbfe9
Signed-off-by: Uilian Ries <uilianries@gmail.com>
@olk
olk merged commit c771a44 into boostorg:developAug 14, 2026
21 of 26 checks passed
@olk

olk commented Aug 14, 2026

Copy link
Copy Markdown
Member

ty

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@uilianries@olk
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
Fix default ABI to allow using target-os instead of the default one - #340
Merged
olk merged 1 commit into
boostorg:developfrom 
uilianries:fix/windows-android
Aug 14, 2026
Merged
Fix default ABI to allow using target-os instead of the default one#340
olk merged 1 commit into
boostorg:developfrom 
uilianries:fix/windows-android
Conversation
@uilianries
@uilianriesuilianries
commented
Aug 10, 2026

Copy link


Copy Markdown

Contributor
Greeting!
After merging PR #334 and #335, when doing a few new validations with Boost 1.92.0-RC1 (se https://lists.boost.org/archives/list/boost@lists.boost.org/thread/U7DDTRXFCNGGZA5XZ5H6ZL2MUEFH5OLM/) I found a missing scenario when cross-building OS, mainly on Windows as host and another OS (e.g. Android) as target. The previous PRs fixed Context's ABI and binary-format defaults to derive from the deduced target (<target-os>/<architecture>) instead of the host platform, which is fine. However, the default_abi() still picks ms instead of the correct target ABI, even with target-os/architecture explicitly passed:
https://github.com/boostorg/context/blob/develop/boost-context-features.jam#L59
rule default_abi ( properties * )
{
local tmp = sysv ;
local arch = [ property.select <architecture> : $(properties) ] ;
if <target-os>windows in $(properties) { tmp = ms ; }
else if <target-os>cygwin in $(properties) { tmp = ms ; }
else if [ os.name ] = "NT" { tmp = ms ; }
else if [ os.name ] = "CYGWIN" { tmp = ms ; }
else if $(arch)
{
if <architecture>arm in $(properties) { tmp = aapcs ; }
else if <architecture>mips in $(properties)
{
if <address-model>64 in $(properties) { tmp = n64 ; }
else { tmp = o32 ; }
}
}

So, in case I try to cross-compile Boost Context from Windows to Android, even passing explicit target-os, abi, address-model, and architecture, I still have the following error during the setup:
error: No best alternative for /C:/Users/uilia/.conan2/p/b/boostbeb40f0cea2a9/b/src/libs/context/build/asm_sources with <abi>ms <address-model>64 <architecture>arm <asynch-exceptions>off <binary-format>elf <boost.beast.allow-deprecated>on <boost.beast.separate-compilation>on <boost.cobalt.executor>any_io_executor <boost.cobalt.pmr>std <boost.locale.iconv>off <boost.locale.icu>off <context-impl>fcontext <coverage>off <debug-symbols>none <exception-handling>on <extern-c-nothrow>off <inlining>none <known-warnings>hide <link>shared <optimization>none <os>NT <pch>on <preserve-test-targets>on <profiling>off <python-debugging>off <relevant>abi <relevant>address-model <relevant>architecture <relevant>binary-format <relevant>toolset <rtti>on <runtime-debugging>none <runtime-link>none <stdlib>native <strip>off <target-os>android <testing.execute>on <threadapi>pthread <threading>multi <toolset-clang:platform>linux <toolset-clang:version>18 <toolset>clang <variant>release <vectorize>off <visibility>hidden <warnings-as-errors>off <warnings>on <x-deduced-platform>arm_64
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>qcc
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>pe <threading>multi <toolset>msvc
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin
...

You can see my full build log with this error here: boost-1.92.0.rc1-windows-android-context.log
As default_abi is wired in as <conditional>@boost-context-features.default_abi, it overrides the explicit abi= on the command line too. So running b2 ... target-os=android architecture=arm abi=aapcs ... still fails the same way on a Windows host, and there's no command-line workaround.
This PR moves the [ os.name ] = "NT"/"CYGWIN" to mirror default_binary_format() structure. The host name is now consulted only when neither <target-os> nor <architecture> was part of the build request, so if a user passes it explicitly, the explicit one should prevail.
With this change, Context picks make_arm64_aapcs_elf_gas.S / jump_arm64_aapcs_elf_gas.S / ontop_arm64_aapcs_elf_gas.S when cross-building from Windows to Android/arm64, same as it already does correctly when cross-building from macOS or Linux.
I built locally, again Windows -> Android, and now I no longer have this error: boost-1.92.0.rc1-windows-android-context-patched.log
Environment
Host OS: Windows 10

Target OS: Android

Compiler: Android (13691557, based on r522817d) clang version 18.0.4 (https://android.googlesource.com/toolchain/llvm-project d8003a456d14a3deb8054cdaa529ffbf02d9b262) - Target:

Boost: 1.92.0-rc1
Steps to Reproduce
I used Conan initially, but I can reproduce when building from sources as well.
wget https://archives.boost.io/release/1.92.0/source/boost_1_92_0_rc1.zip
unzip boost_1_92_0_rc1.zip
cd boost_1_92_0/
bootstrap.bat
set "CXX=C:/Users/uilia/Development/android-ndk-r27d/toolchains/llvm/prebuilt/windows-x86_64/bin/aarch64-linux-android27-clang++.cmd"
b2 install target-os=android architecture=arm abi=aapcs binary-format=elf architecture=arm address-model=64 -d2 -q toolset=clang --layout=system

Note that as I'm cross-building, I have NDK 27d installed in my Windows, the official one from Android page. Android is just example, cross-building to Linux should result in the same.
Tell me if you need further validation or information about the case. Regards!
@uilianries
Fix when cross-building OS
54bbfe9
Signed-off-by: Uilian Ries <uilianries@gmail.com>
@olk
olk
merged commit c771a44
into
boostorg:developAug 14, 2026

21 of 26 checks passed

@olk
olk
commented
Aug 14, 2026

Copy link


Copy Markdown

Member
ty
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@uilianries@olk

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Fix default ABI to allow using target-os instead of the default one - #340
Merged
olk merged 1 commit into
boostorg:developfrom 
uilianries:fix/windows-android
Aug 14, 2026
Merged
Fix default ABI to allow using target-os instead of the default one#340
olk merged 1 commit into
boostorg:developfrom 
uilianries:fix/windows-android
Conversation
@uilianries
@uilianriesuilianries
commented
Aug 10, 2026

Copy link


Copy Markdown

Contributor
Greeting!
After merging PR #334 and #335, when doing a few new validations with Boost 1.92.0-RC1 (se https://lists.boost.org/archives/list/boost@lists.boost.org/thread/U7DDTRXFCNGGZA5XZ5H6ZL2MUEFH5OLM/) I found a missing scenario when cross-building OS, mainly on Windows as host and another OS (e.g. Android) as target. The previous PRs fixed Context's ABI and binary-format defaults to derive from the deduced target (<target-os>/<architecture>) instead of the host platform, which is fine. However, the default_abi() still picks ms instead of the correct target ABI, even with target-os/architecture explicitly passed:
https://github.com/boostorg/context/blob/develop/boost-context-features.jam#L59
rule default_abi ( properties * )
{
local tmp = sysv ;
local arch = [ property.select <architecture> : $(properties) ] ;
if <target-os>windows in $(properties) { tmp = ms ; }
else if <target-os>cygwin in $(properties) { tmp = ms ; }
else if [ os.name ] = "NT" { tmp = ms ; }
else if [ os.name ] = "CYGWIN" { tmp = ms ; }
else if $(arch)
{
if <architecture>arm in $(properties) { tmp = aapcs ; }
else if <architecture>mips in $(properties)
{
if <address-model>64 in $(properties) { tmp = n64 ; }
else { tmp = o32 ; }
}
}

So, in case I try to cross-compile Boost Context from Windows to Android, even passing explicit target-os, abi, address-model, and architecture, I still have the following error during the setup:
error: No best alternative for /C:/Users/uilia/.conan2/p/b/boostbeb40f0cea2a9/b/src/libs/context/build/asm_sources with <abi>ms <address-model>64 <architecture>arm <asynch-exceptions>off <binary-format>elf <boost.beast.allow-deprecated>on <boost.beast.separate-compilation>on <boost.cobalt.executor>any_io_executor <boost.cobalt.pmr>std <boost.locale.iconv>off <boost.locale.icu>off <context-impl>fcontext <coverage>off <debug-symbols>none <exception-handling>on <extern-c-nothrow>off <inlining>none <known-warnings>hide <link>shared <optimization>none <os>NT <pch>on <preserve-test-targets>on <profiling>off <python-debugging>off <relevant>abi <relevant>address-model <relevant>architecture <relevant>binary-format <relevant>toolset <rtti>on <runtime-debugging>none <runtime-link>none <stdlib>native <strip>off <target-os>android <testing.execute>on <threadapi>pthread <threading>multi <toolset-clang:platform>linux <toolset-clang:version>18 <toolset>clang <variant>release <vectorize>off <visibility>hidden <warnings-as-errors>off <warnings>on <x-deduced-platform>arm_64
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>qcc
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>pe <threading>multi <toolset>msvc
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin
...

You can see my full build log with this error here: boost-1.92.0.rc1-windows-android-context.log
As default_abi is wired in as <conditional>@boost-context-features.default_abi, it overrides the explicit abi= on the command line too. So running b2 ... target-os=android architecture=arm abi=aapcs ... still fails the same way on a Windows host, and there's no command-line workaround.
This PR moves the [ os.name ] = "NT"/"CYGWIN" to mirror default_binary_format() structure. The host name is now consulted only when neither <target-os> nor <architecture> was part of the build request, so if a user passes it explicitly, the explicit one should prevail.
With this change, Context picks make_arm64_aapcs_elf_gas.S / jump_arm64_aapcs_elf_gas.S / ontop_arm64_aapcs_elf_gas.S when cross-building from Windows to Android/arm64, same as it already does correctly when cross-building from macOS or Linux.
I built locally, again Windows -> Android, and now I no longer have this error: boost-1.92.0.rc1-windows-android-context-patched.log
Environment
Host OS: Windows 10

Target OS: Android

Compiler: Android (13691557, based on r522817d) clang version 18.0.4 (https://android.googlesource.com/toolchain/llvm-project d8003a456d14a3deb8054cdaa529ffbf02d9b262) - Target:

Boost: 1.92.0-rc1
Steps to Reproduce
I used Conan initially, but I can reproduce when building from sources as well.
wget https://archives.boost.io/release/1.92.0/source/boost_1_92_0_rc1.zip
unzip boost_1_92_0_rc1.zip
cd boost_1_92_0/
bootstrap.bat
set "CXX=C:/Users/uilia/Development/android-ndk-r27d/toolchains/llvm/prebuilt/windows-x86_64/bin/aarch64-linux-android27-clang++.cmd"
b2 install target-os=android architecture=arm abi=aapcs binary-format=elf architecture=arm address-model=64 -d2 -q toolset=clang --layout=system

Note that as I'm cross-building, I have NDK 27d installed in my Windows, the official one from Android page. Android is just example, cross-building to Linux should result in the same.
Tell me if you need further validation or information about the case. Regards!
@uilianries
Fix when cross-building OS
54bbfe9
Signed-off-by: Uilian Ries <uilianries@gmail.com>
@olk
olk
merged commit c771a44
into
boostorg:developAug 14, 2026

21 of 26 checks passed

@olk
olk
commented
Aug 14, 2026

Copy link


Copy Markdown

Member
ty
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@uilianries@olk

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Fix default ABI to allow using target-os instead of the default one - #340
Merged
olk merged 1 commit into
boostorg:developfrom 
uilianries:fix/windows-android
Aug 14, 2026
Merged
Fix default ABI to allow using target-os instead of the default one#340
olk merged 1 commit into
boostorg:developfrom 
uilianries:fix/windows-android
Conversation
@uilianries
@uilianriesuilianries
commented
Aug 10, 2026

Copy link


Copy Markdown

Contributor
Greeting!
After merging PR #334 and #335, when doing a few new validations with Boost 1.92.0-RC1 (se https://lists.boost.org/archives/list/boost@lists.boost.org/thread/U7DDTRXFCNGGZA5XZ5H6ZL2MUEFH5OLM/) I found a missing scenario when cross-building OS, mainly on Windows as host and another OS (e.g. Android) as target. The previous PRs fixed Context's ABI and binary-format defaults to derive from the deduced target (<target-os>/<architecture>) instead of the host platform, which is fine. However, the default_abi() still picks ms instead of the correct target ABI, even with target-os/architecture explicitly passed:
https://github.com/boostorg/context/blob/develop/boost-context-features.jam#L59
rule default_abi ( properties * )
{
local tmp = sysv ;
local arch = [ property.select <architecture> : $(properties) ] ;
if <target-os>windows in $(properties) { tmp = ms ; }
else if <target-os>cygwin in $(properties) { tmp = ms ; }
else if [ os.name ] = "NT" { tmp = ms ; }
else if [ os.name ] = "CYGWIN" { tmp = ms ; }
else if $(arch)
{
if <architecture>arm in $(properties) { tmp = aapcs ; }
else if <architecture>mips in $(properties)
{
if <address-model>64 in $(properties) { tmp = n64 ; }
else { tmp = o32 ; }
}
}

So, in case I try to cross-compile Boost Context from Windows to Android, even passing explicit target-os, abi, address-model, and architecture, I still have the following error during the setup:
error: No best alternative for /C:/Users/uilia/.conan2/p/b/boostbeb40f0cea2a9/b/src/libs/context/build/asm_sources with <abi>ms <address-model>64 <architecture>arm <asynch-exceptions>off <binary-format>elf <boost.beast.allow-deprecated>on <boost.beast.separate-compilation>on <boost.cobalt.executor>any_io_executor <boost.cobalt.pmr>std <boost.locale.iconv>off <boost.locale.icu>off <context-impl>fcontext <coverage>off <debug-symbols>none <exception-handling>on <extern-c-nothrow>off <inlining>none <known-warnings>hide <link>shared <optimization>none <os>NT <pch>on <preserve-test-targets>on <profiling>off <python-debugging>off <relevant>abi <relevant>address-model <relevant>architecture <relevant>binary-format <relevant>toolset <rtti>on <runtime-debugging>none <runtime-link>none <stdlib>native <strip>off <target-os>android <testing.execute>on <threadapi>pthread <threading>multi <toolset-clang:platform>linux <toolset-clang:version>18 <toolset>clang <variant>release <vectorize>off <visibility>hidden <warnings-as-errors>off <warnings>on <x-deduced-platform>arm_64
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>qcc
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>pe <threading>multi <toolset>msvc
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin
...

You can see my full build log with this error here: boost-1.92.0.rc1-windows-android-context.log
As default_abi is wired in as <conditional>@boost-context-features.default_abi, it overrides the explicit abi= on the command line too. So running b2 ... target-os=android architecture=arm abi=aapcs ... still fails the same way on a Windows host, and there's no command-line workaround.
This PR moves the [ os.name ] = "NT"/"CYGWIN" to mirror default_binary_format() structure. The host name is now consulted only when neither <target-os> nor <architecture> was part of the build request, so if a user passes it explicitly, the explicit one should prevail.
With this change, Context picks make_arm64_aapcs_elf_gas.S / jump_arm64_aapcs_elf_gas.S / ontop_arm64_aapcs_elf_gas.S when cross-building from Windows to Android/arm64, same as it already does correctly when cross-building from macOS or Linux.
I built locally, again Windows -> Android, and now I no longer have this error: boost-1.92.0.rc1-windows-android-context-patched.log
Environment
Host OS: Windows 10

Target OS: Android

Compiler: Android (13691557, based on r522817d) clang version 18.0.4 (https://android.googlesource.com/toolchain/llvm-project d8003a456d14a3deb8054cdaa529ffbf02d9b262) - Target:

Boost: 1.92.0-rc1
Steps to Reproduce
I used Conan initially, but I can reproduce when building from sources as well.
wget https://archives.boost.io/release/1.92.0/source/boost_1_92_0_rc1.zip
unzip boost_1_92_0_rc1.zip
cd boost_1_92_0/
bootstrap.bat
set "CXX=C:/Users/uilia/Development/android-ndk-r27d/toolchains/llvm/prebuilt/windows-x86_64/bin/aarch64-linux-android27-clang++.cmd"
b2 install target-os=android architecture=arm abi=aapcs binary-format=elf architecture=arm address-model=64 -d2 -q toolset=clang --layout=system

Note that as I'm cross-building, I have NDK 27d installed in my Windows, the official one from Android page. Android is just example, cross-building to Linux should result in the same.
Tell me if you need further validation or information about the case. Regards!
@uilianries
Fix when cross-building OS
54bbfe9
Signed-off-by: Uilian Ries <uilianries@gmail.com>
@olk
olk
merged commit c771a44
into
boostorg:developAug 14, 2026

21 of 26 checks passed

@olk
olk
commented
Aug 14, 2026

Copy link


Copy Markdown

Member
ty
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@uilianries@olk

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
Fix default ABI to allow using target-os instead of the default one - #340
Merged
olk merged 1 commit into
boostorg:developfrom 
uilianries:fix/windows-android
Aug 14, 2026
Merged
Fix default ABI to allow using target-os instead of the default one#340
olk merged 1 commit into
boostorg:developfrom 
uilianries:fix/windows-android
Conversation
@uilianries
@uilianriesuilianries
commented
Aug 10, 2026

Copy link


Copy Markdown

Contributor
Greeting!
After merging PR #334 and #335, when doing a few new validations with Boost 1.92.0-RC1 (se https://lists.boost.org/archives/list/boost@lists.boost.org/thread/U7DDTRXFCNGGZA5XZ5H6ZL2MUEFH5OLM/) I found a missing scenario when cross-building OS, mainly on Windows as host and another OS (e.g. Android) as target. The previous PRs fixed Context's ABI and binary-format defaults to derive from the deduced target (<target-os>/<architecture>) instead of the host platform, which is fine. However, the default_abi() still picks ms instead of the correct target ABI, even with target-os/architecture explicitly passed:
https://github.com/boostorg/context/blob/develop/boost-context-features.jam#L59
rule default_abi ( properties * )
{
local tmp = sysv ;
local arch = [ property.select <architecture> : $(properties) ] ;
if <target-os>windows in $(properties) { tmp = ms ; }
else if <target-os>cygwin in $(properties) { tmp = ms ; }
else if [ os.name ] = "NT" { tmp = ms ; }
else if [ os.name ] = "CYGWIN" { tmp = ms ; }
else if $(arch)
{
if <architecture>arm in $(properties) { tmp = aapcs ; }
else if <architecture>mips in $(properties)
{
if <address-model>64 in $(properties) { tmp = n64 ; }
else { tmp = o32 ; }
}
}

So, in case I try to cross-compile Boost Context from Windows to Android, even passing explicit target-os, abi, address-model, and architecture, I still have the following error during the setup:
error: No best alternative for /C:/Users/uilia/.conan2/p/b/boostbeb40f0cea2a9/b/src/libs/context/build/asm_sources with <abi>ms <address-model>64 <architecture>arm <asynch-exceptions>off <binary-format>elf <boost.beast.allow-deprecated>on <boost.beast.separate-compilation>on <boost.cobalt.executor>any_io_executor <boost.cobalt.pmr>std <boost.locale.iconv>off <boost.locale.icu>off <context-impl>fcontext <coverage>off <debug-symbols>none <exception-handling>on <extern-c-nothrow>off <inlining>none <known-warnings>hide <link>shared <optimization>none <os>NT <pch>on <preserve-test-targets>on <profiling>off <python-debugging>off <relevant>abi <relevant>address-model <relevant>architecture <relevant>binary-format <relevant>toolset <rtti>on <runtime-debugging>none <runtime-link>none <stdlib>native <strip>off <target-os>android <testing.execute>on <threadapi>pthread <threading>multi <toolset-clang:platform>linux <toolset-clang:version>18 <toolset>clang <variant>release <vectorize>off <visibility>hidden <warnings-as-errors>off <warnings>on <x-deduced-platform>arm_64
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>qcc
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>pe <threading>multi <toolset>msvc
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin
...

You can see my full build log with this error here: boost-1.92.0.rc1-windows-android-context.log
As default_abi is wired in as <conditional>@boost-context-features.default_abi, it overrides the explicit abi= on the command line too. So running b2 ... target-os=android architecture=arm abi=aapcs ... still fails the same way on a Windows host, and there's no command-line workaround.
This PR moves the [ os.name ] = "NT"/"CYGWIN" to mirror default_binary_format() structure. The host name is now consulted only when neither <target-os> nor <architecture> was part of the build request, so if a user passes it explicitly, the explicit one should prevail.
With this change, Context picks make_arm64_aapcs_elf_gas.S / jump_arm64_aapcs_elf_gas.S / ontop_arm64_aapcs_elf_gas.S when cross-building from Windows to Android/arm64, same as it already does correctly when cross-building from macOS or Linux.
I built locally, again Windows -> Android, and now I no longer have this error: boost-1.92.0.rc1-windows-android-context-patched.log
Environment
Host OS: Windows 10

Target OS: Android

Compiler: Android (13691557, based on r522817d) clang version 18.0.4 (https://android.googlesource.com/toolchain/llvm-project d8003a456d14a3deb8054cdaa529ffbf02d9b262) - Target:

Boost: 1.92.0-rc1
Steps to Reproduce
I used Conan initially, but I can reproduce when building from sources as well.
wget https://archives.boost.io/release/1.92.0/source/boost_1_92_0_rc1.zip
unzip boost_1_92_0_rc1.zip
cd boost_1_92_0/
bootstrap.bat
set "CXX=C:/Users/uilia/Development/android-ndk-r27d/toolchains/llvm/prebuilt/windows-x86_64/bin/aarch64-linux-android27-clang++.cmd"
b2 install target-os=android architecture=arm abi=aapcs binary-format=elf architecture=arm address-model=64 -d2 -q toolset=clang --layout=system

Note that as I'm cross-building, I have NDK 27d installed in my Windows, the official one from Android page. Android is just example, cross-building to Linux should result in the same.
Tell me if you need further validation or information about the case. Regards!
@uilianries
Fix when cross-building OS
54bbfe9
Signed-off-by: Uilian Ries <uilianries@gmail.com>
@olk
olk
merged commit c771a44
into
boostorg:developAug 14, 2026

21 of 26 checks passed

@olk
olk
commented
Aug 14, 2026

Copy link


Copy Markdown

Member
ty
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@uilianries@olk

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Fix default ABI to allow using target-os instead of the default one - #340
Merged
olk merged 1 commit into
boostorg:developfrom 
uilianries:fix/windows-android
Aug 14, 2026
Merged
Fix default ABI to allow using target-os instead of the default one#340
olk merged 1 commit into
boostorg:developfrom 
uilianries:fix/windows-android
Conversation
@uilianries
@uilianriesuilianries
commented
Aug 10, 2026

Copy link


Copy Markdown

Contributor
Greeting!
After merging PR #334 and #335, when doing a few new validations with Boost 1.92.0-RC1 (se https://lists.boost.org/archives/list/boost@lists.boost.org/thread/U7DDTRXFCNGGZA5XZ5H6ZL2MUEFH5OLM/) I found a missing scenario when cross-building OS, mainly on Windows as host and another OS (e.g. Android) as target. The previous PRs fixed Context's ABI and binary-format defaults to derive from the deduced target (<target-os>/<architecture>) instead of the host platform, which is fine. However, the default_abi() still picks ms instead of the correct target ABI, even with target-os/architecture explicitly passed:
https://github.com/boostorg/context/blob/develop/boost-context-features.jam#L59
rule default_abi ( properties * )
{
local tmp = sysv ;
local arch = [ property.select <architecture> : $(properties) ] ;
if <target-os>windows in $(properties) { tmp = ms ; }
else if <target-os>cygwin in $(properties) { tmp = ms ; }
else if [ os.name ] = "NT" { tmp = ms ; }
else if [ os.name ] = "CYGWIN" { tmp = ms ; }
else if $(arch)
{
if <architecture>arm in $(properties) { tmp = aapcs ; }
else if <architecture>mips in $(properties)
{
if <address-model>64 in $(properties) { tmp = n64 ; }
else { tmp = o32 ; }
}
}

So, in case I try to cross-compile Boost Context from Windows to Android, even passing explicit target-os, abi, address-model, and architecture, I still have the following error during the setup:
error: No best alternative for /C:/Users/uilia/.conan2/p/b/boostbeb40f0cea2a9/b/src/libs/context/build/asm_sources with <abi>ms <address-model>64 <architecture>arm <asynch-exceptions>off <binary-format>elf <boost.beast.allow-deprecated>on <boost.beast.separate-compilation>on <boost.cobalt.executor>any_io_executor <boost.cobalt.pmr>std <boost.locale.iconv>off <boost.locale.icu>off <context-impl>fcontext <coverage>off <debug-symbols>none <exception-handling>on <extern-c-nothrow>off <inlining>none <known-warnings>hide <link>shared <optimization>none <os>NT <pch>on <preserve-test-targets>on <profiling>off <python-debugging>off <relevant>abi <relevant>address-model <relevant>architecture <relevant>binary-format <relevant>toolset <rtti>on <runtime-debugging>none <runtime-link>none <stdlib>native <strip>off <target-os>android <testing.execute>on <threadapi>pthread <threading>multi <toolset-clang:platform>linux <toolset-clang:version>18 <toolset>clang <variant>release <vectorize>off <visibility>hidden <warnings-as-errors>off <warnings>on <x-deduced-platform>arm_64
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>qcc
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>pe <threading>multi <toolset>msvc
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin
...

You can see my full build log with this error here: boost-1.92.0.rc1-windows-android-context.log
As default_abi is wired in as <conditional>@boost-context-features.default_abi, it overrides the explicit abi= on the command line too. So running b2 ... target-os=android architecture=arm abi=aapcs ... still fails the same way on a Windows host, and there's no command-line workaround.
This PR moves the [ os.name ] = "NT"/"CYGWIN" to mirror default_binary_format() structure. The host name is now consulted only when neither <target-os> nor <architecture> was part of the build request, so if a user passes it explicitly, the explicit one should prevail.
With this change, Context picks make_arm64_aapcs_elf_gas.S / jump_arm64_aapcs_elf_gas.S / ontop_arm64_aapcs_elf_gas.S when cross-building from Windows to Android/arm64, same as it already does correctly when cross-building from macOS or Linux.
I built locally, again Windows -> Android, and now I no longer have this error: boost-1.92.0.rc1-windows-android-context-patched.log
Environment
Host OS: Windows 10

Target OS: Android

Compiler: Android (13691557, based on r522817d) clang version 18.0.4 (https://android.googlesource.com/toolchain/llvm-project d8003a456d14a3deb8054cdaa529ffbf02d9b262) - Target:

Boost: 1.92.0-rc1
Steps to Reproduce
I used Conan initially, but I can reproduce when building from sources as well.
wget https://archives.boost.io/release/1.92.0/source/boost_1_92_0_rc1.zip
unzip boost_1_92_0_rc1.zip
cd boost_1_92_0/
bootstrap.bat
set "CXX=C:/Users/uilia/Development/android-ndk-r27d/toolchains/llvm/prebuilt/windows-x86_64/bin/aarch64-linux-android27-clang++.cmd"
b2 install target-os=android architecture=arm abi=aapcs binary-format=elf architecture=arm address-model=64 -d2 -q toolset=clang --layout=system

Note that as I'm cross-building, I have NDK 27d installed in my Windows, the official one from Android page. Android is just example, cross-building to Linux should result in the same.
Tell me if you need further validation or information about the case. Regards!
@uilianries
Fix when cross-building OS
54bbfe9
Signed-off-by: Uilian Ries <uilianries@gmail.com>
@olk
olk
merged commit c771a44
into
boostorg:developAug 14, 2026

21 of 26 checks passed

@olk
olk
commented
Aug 14, 2026

Copy link


Copy Markdown

Member
ty
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@uilianries@olk

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Fix default ABI to allow using target-os instead of the default one - #340
Merged
olk merged 1 commit into
boostorg:developfrom 
uilianries:fix/windows-android
Aug 14, 2026
Merged
Fix default ABI to allow using target-os instead of the default one#340
olk merged 1 commit into
boostorg:developfrom 
uilianries:fix/windows-android
Conversation
@uilianries
@uilianriesuilianries
commented
Aug 10, 2026

Copy link


Copy Markdown

Contributor
Greeting!
After merging PR #334 and #335, when doing a few new validations with Boost 1.92.0-RC1 (se https://lists.boost.org/archives/list/boost@lists.boost.org/thread/U7DDTRXFCNGGZA5XZ5H6ZL2MUEFH5OLM/) I found a missing scenario when cross-building OS, mainly on Windows as host and another OS (e.g. Android) as target. The previous PRs fixed Context's ABI and binary-format defaults to derive from the deduced target (<target-os>/<architecture>) instead of the host platform, which is fine. However, the default_abi() still picks ms instead of the correct target ABI, even with target-os/architecture explicitly passed:
https://github.com/boostorg/context/blob/develop/boost-context-features.jam#L59
rule default_abi ( properties * )
{
local tmp = sysv ;
local arch = [ property.select <architecture> : $(properties) ] ;
if <target-os>windows in $(properties) { tmp = ms ; }
else if <target-os>cygwin in $(properties) { tmp = ms ; }
else if [ os.name ] = "NT" { tmp = ms ; }
else if [ os.name ] = "CYGWIN" { tmp = ms ; }
else if $(arch)
{
if <architecture>arm in $(properties) { tmp = aapcs ; }
else if <architecture>mips in $(properties)
{
if <address-model>64 in $(properties) { tmp = n64 ; }
else { tmp = o32 ; }
}
}

So, in case I try to cross-compile Boost Context from Windows to Android, even passing explicit target-os, abi, address-model, and architecture, I still have the following error during the setup:
error: No best alternative for /C:/Users/uilia/.conan2/p/b/boostbeb40f0cea2a9/b/src/libs/context/build/asm_sources with <abi>ms <address-model>64 <architecture>arm <asynch-exceptions>off <binary-format>elf <boost.beast.allow-deprecated>on <boost.beast.separate-compilation>on <boost.cobalt.executor>any_io_executor <boost.cobalt.pmr>std <boost.locale.iconv>off <boost.locale.icu>off <context-impl>fcontext <coverage>off <debug-symbols>none <exception-handling>on <extern-c-nothrow>off <inlining>none <known-warnings>hide <link>shared <optimization>none <os>NT <pch>on <preserve-test-targets>on <profiling>off <python-debugging>off <relevant>abi <relevant>address-model <relevant>architecture <relevant>binary-format <relevant>toolset <rtti>on <runtime-debugging>none <runtime-link>none <stdlib>native <strip>off <target-os>android <testing.execute>on <threadapi>pthread <threading>multi <toolset-clang:platform>linux <toolset-clang:version>18 <toolset>clang <variant>release <vectorize>off <visibility>hidden <warnings-as-errors>off <warnings>on <x-deduced-platform>arm_64
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>qcc
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>pe <threading>multi <toolset>msvc
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin
...

You can see my full build log with this error here: boost-1.92.0.rc1-windows-android-context.log
As default_abi is wired in as <conditional>@boost-context-features.default_abi, it overrides the explicit abi= on the command line too. So running b2 ... target-os=android architecture=arm abi=aapcs ... still fails the same way on a Windows host, and there's no command-line workaround.
This PR moves the [ os.name ] = "NT"/"CYGWIN" to mirror default_binary_format() structure. The host name is now consulted only when neither <target-os> nor <architecture> was part of the build request, so if a user passes it explicitly, the explicit one should prevail.
With this change, Context picks make_arm64_aapcs_elf_gas.S / jump_arm64_aapcs_elf_gas.S / ontop_arm64_aapcs_elf_gas.S when cross-building from Windows to Android/arm64, same as it already does correctly when cross-building from macOS or Linux.
I built locally, again Windows -> Android, and now I no longer have this error: boost-1.92.0.rc1-windows-android-context-patched.log
Environment
Host OS: Windows 10

Target OS: Android

Compiler: Android (13691557, based on r522817d) clang version 18.0.4 (https://android.googlesource.com/toolchain/llvm-project d8003a456d14a3deb8054cdaa529ffbf02d9b262) - Target:

Boost: 1.92.0-rc1
Steps to Reproduce
I used Conan initially, but I can reproduce when building from sources as well.
wget https://archives.boost.io/release/1.92.0/source/boost_1_92_0_rc1.zip
unzip boost_1_92_0_rc1.zip
cd boost_1_92_0/
bootstrap.bat
set "CXX=C:/Users/uilia/Development/android-ndk-r27d/toolchains/llvm/prebuilt/windows-x86_64/bin/aarch64-linux-android27-clang++.cmd"
b2 install target-os=android architecture=arm abi=aapcs binary-format=elf architecture=arm address-model=64 -d2 -q toolset=clang --layout=system

Note that as I'm cross-building, I have NDK 27d installed in my Windows, the official one from Android page. Android is just example, cross-building to Linux should result in the same.
Tell me if you need further validation or information about the case. Regards!
@uilianries
Fix when cross-building OS
54bbfe9
Signed-off-by: Uilian Ries <uilianries@gmail.com>
@olk
olk
merged commit c771a44
into
boostorg:developAug 14, 2026

21 of 26 checks passed

@olk
olk
commented
Aug 14, 2026

Copy link


Copy Markdown

Member
ty
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@uilianries@olk

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
Fix default ABI to allow using target-os instead of the default one - #340
Merged
olk merged 1 commit into
boostorg:developfrom 
uilianries:fix/windows-android
Aug 14, 2026
Merged
Fix default ABI to allow using target-os instead of the default one#340
olk merged 1 commit into
boostorg:developfrom 
uilianries:fix/windows-android
Conversation
@uilianries
@uilianriesuilianries
commented
Aug 10, 2026

Copy link


Copy Markdown

Contributor
Greeting!
After merging PR #334 and #335, when doing a few new validations with Boost 1.92.0-RC1 (se https://lists.boost.org/archives/list/boost@lists.boost.org/thread/U7DDTRXFCNGGZA5XZ5H6ZL2MUEFH5OLM/) I found a missing scenario when cross-building OS, mainly on Windows as host and another OS (e.g. Android) as target. The previous PRs fixed Context's ABI and binary-format defaults to derive from the deduced target (<target-os>/<architecture>) instead of the host platform, which is fine. However, the default_abi() still picks ms instead of the correct target ABI, even with target-os/architecture explicitly passed:
https://github.com/boostorg/context/blob/develop/boost-context-features.jam#L59
rule default_abi ( properties * )
{
local tmp = sysv ;
local arch = [ property.select <architecture> : $(properties) ] ;
if <target-os>windows in $(properties) { tmp = ms ; }
else if <target-os>cygwin in $(properties) { tmp = ms ; }
else if [ os.name ] = "NT" { tmp = ms ; }
else if [ os.name ] = "CYGWIN" { tmp = ms ; }
else if $(arch)
{
if <architecture>arm in $(properties) { tmp = aapcs ; }
else if <architecture>mips in $(properties)
{
if <address-model>64 in $(properties) { tmp = n64 ; }
else { tmp = o32 ; }
}
}

So, in case I try to cross-compile Boost Context from Windows to Android, even passing explicit target-os, abi, address-model, and architecture, I still have the following error during the setup:
error: No best alternative for /C:/Users/uilia/.conan2/p/b/boostbeb40f0cea2a9/b/src/libs/context/build/asm_sources with <abi>ms <address-model>64 <architecture>arm <asynch-exceptions>off <binary-format>elf <boost.beast.allow-deprecated>on <boost.beast.separate-compilation>on <boost.cobalt.executor>any_io_executor <boost.cobalt.pmr>std <boost.locale.iconv>off <boost.locale.icu>off <context-impl>fcontext <coverage>off <debug-symbols>none <exception-handling>on <extern-c-nothrow>off <inlining>none <known-warnings>hide <link>shared <optimization>none <os>NT <pch>on <preserve-test-targets>on <profiling>off <python-debugging>off <relevant>abi <relevant>address-model <relevant>architecture <relevant>binary-format <relevant>toolset <rtti>on <runtime-debugging>none <runtime-link>none <stdlib>native <strip>off <target-os>android <testing.execute>on <threadapi>pthread <threading>multi <toolset-clang:platform>linux <toolset-clang:version>18 <toolset>clang <variant>release <vectorize>off <visibility>hidden <warnings-as-errors>off <warnings>on <x-deduced-platform>arm_64
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>qcc
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin
no match: <abi>aapcs <address-model>32 <architecture>arm <binary-format>pe <threading>multi <toolset>msvc
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang
no match: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin
...

You can see my full build log with this error here: boost-1.92.0.rc1-windows-android-context.log
As default_abi is wired in as <conditional>@boost-context-features.default_abi, it overrides the explicit abi= on the command line too. So running b2 ... target-os=android architecture=arm abi=aapcs ... still fails the same way on a Windows host, and there's no command-line workaround.
This PR moves the [ os.name ] = "NT"/"CYGWIN" to mirror default_binary_format() structure. The host name is now consulted only when neither <target-os> nor <architecture> was part of the build request, so if a user passes it explicitly, the explicit one should prevail.
With this change, Context picks make_arm64_aapcs_elf_gas.S / jump_arm64_aapcs_elf_gas.S / ontop_arm64_aapcs_elf_gas.S when cross-building from Windows to Android/arm64, same as it already does correctly when cross-building from macOS or Linux.
I built locally, again Windows -> Android, and now I no longer have this error: boost-1.92.0.rc1-windows-android-context-patched.log
Environment
Host OS: Windows 10

Target OS: Android

Compiler: Android (13691557, based on r522817d) clang version 18.0.4 (https://android.googlesource.com/toolchain/llvm-project d8003a456d14a3deb8054cdaa529ffbf02d9b262) - Target:

Boost: 1.92.0-rc1
Steps to Reproduce
I used Conan initially, but I can reproduce when building from sources as well.
wget https://archives.boost.io/release/1.92.0/source/boost_1_92_0_rc1.zip
unzip boost_1_92_0_rc1.zip
cd boost_1_92_0/
bootstrap.bat
set "CXX=C:/Users/uilia/Development/android-ndk-r27d/toolchains/llvm/prebuilt/windows-x86_64/bin/aarch64-linux-android27-clang++.cmd"
b2 install target-os=android architecture=arm abi=aapcs binary-format=elf architecture=arm address-model=64 -d2 -q toolset=clang --layout=system

Note that as I'm cross-building, I have NDK 27d installed in my Windows, the official one from Android page. Android is just example, cross-building to Linux should result in the same.
Tell me if you need further validation or information about the case. Regards!
@uilianries
Fix when cross-building OS
54bbfe9
Signed-off-by: Uilian Ries <uilianries@gmail.com>
@olk
olk
merged commit c771a44
into
boostorg:developAug 14, 2026

21 of 26 checks passed

@olk
olk
commented
Aug 14, 2026

Copy link


Copy Markdown

Member
ty
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment

Reviewers


No reviews


Assignees


No one assigned


Labels


None yet


Projects


None yet


Milestone


No milestone


Development

Successfully merging this pull request may close these issues.

2 participants

@uilianries@olk