continue 2

Author: mara004

.github/workflows/cibuildwheel.yaml

@@ -59,7 +59,7 @@ jobs:
           
           def job(image, os, arch, emulated=False):
               matrix.append(dict(
-                  image=image, os=os, arch=arch, needs_emulator=emulated
+                  image=image, os=os, arch=arch, emulated=emulated
               ))
           
           def linux_job(os, arch, emulated=False, images=images):
@@ -103,7 +103,7 @@ jobs:
           fetch-depth: 0
 
       - name: Set up QEMU
-        if: ${{ matrix.needs_emulator }}
+        if: ${{ matrix.emulated }}
         uses: docker/setup-qemu-action@v3
 
       # Reminder: most configuration is in pyproject.toml so we can use TOML overrides

docs/devel/changelog_staging.md

@@ -47,6 +47,7 @@
   Android `arm64_v8a`, `armeabi_v7a`, `x86_64`, `x86` and iOS `arm64` device and `arm64`, `x86_64` simulators are now handled in setup and should implicitly download the right pdfium-binaries. Provided on a best effort basis, and largely untested. Testers/feedback welcome.
 - pypdfium2's setup is now also capable of producing wheels for these platforms, but they will not actually be included in releases at this time. (Once Termux ships Python 3.13, we may want to publish Android `arm64_v8a` and maybe `armeabi_v7a` wheels, but we do not intend to provide wheels for simulators.)
 - iOS will not actually work yet, as the PEP indicates binaries ought to be moved to a special Frameworks location for permission reasons, in which case you'd also have to patch pypdfium2's library search. We cannot do anything about this yet without access to a device or clearer instructions. Community help would be appreciated here.
+- Added draft cibuildwheel workflow and configuration, as a second footing for the project (based on the native sourcebuild, see below). In the future, this might allow us to stuff some Linux architecture gaps the *quick & dirty* way with emulation, or maybe new native runners. Many thanks to `wojiushixiaobai` for providing the initial pointers.
 
 *Setup*
 - When pdfium binaries are downloaded implicitly on setup or `emplace.py` is run, we now pin the pdfium version by default. This is to prevent possible API breakage when pypdfium2 is installed from source. It should also make the `git` dependency optional on default setup. `update.py` and `craft.py` continue to default to the latest pdfium-binaries version.