David Sungaila

> I'm starting to feel like I'm the only one using the WebAssembly build :D There are at least two. I have two GitHub pages hosted right now using these...

> Honestly, this sounds like a major design flaw in the .NET WASM support? But seeing how they integrate the library (with the .a file and not the .wasm file),...

It would be great if the the iOS dylib would come prepacked as a framework. I would take care to include them [into the NuGet package](https://www.nuget.org/packages/bblanchon.PDFium.iOS/). Otherwise, a static lib...

> Don't I need a certificate to codesign? I am not sure. I have seen unsigned frameworks, in these cases the developer will have to sign these themselves before submitting...

Hi @torfluor, if you can help to create iOS and Catalyst binaries for pdfium, I'll add the missing NuGet packages needed for MAUI. I don't have a Mac myself to...

I've tried for a few hours to get this working in my fork but I couldn't do it. The pdfium build files don't have catalyst as a target and I'm...

AFAIK Mac Catalyst is its own build target for dylibs consumed by both macOS and iOS (plus derivatives like iPadOS). .NET has the `maccatalyst` target to seperate it from `osx`...

So maybe the pdfium build should be run with `mac` as `target_os` but with slight compiler argument changes? Like setting the Mac Catalyst ABI and a higher SDK version?

[The hosted runners by GitHub have Xcode preinstalled.](https://github.com/actions/runner-images/blob/main/images/macos/macos-14-Readme.md) But I personally would prefer a clean build over a hack (which is not yet confirmed to run on iOS).

Maybe the `mac_deployment_target` could be set higher as a compromise. I mean besides the `vtool` hacking.