You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While cross-compilation for iOS-derived devices is possible and Meson successfully generates standalone binaries, I have not found a straightforward way to create a framework bundle (e.g., bundling Info.plist, public headers, and the binary into a .framework artifact).
This functionality is available by setting properties in build configurations of various build systems, such as CMake. However, I have not seen anything similar in Meson, nor do I know if it's planned for future implementation.
system parameters
Is this a cross build or just a plain native build (for the same computer)? - It could be either a native build or for an iOS-derived device.
what operating system (e.g. MacOS Catalina, Windows 10, CentOS 8.0, Ubuntu 18.04, etc.) - macOS Sequoia
what Python version are you using e.g. 3.8.0 - Python 3.13.2
what meson --version - Meson 1.7.0
what ninja --version if it's a Ninja build - -
The text was updated successfully, but these errors were encountered:
Would love to see this! There's a tutorial for bundles on the Meson website (link), but it's really complicated. I would like to see some kind of bundle function, where you can outline a directory structure to support other kinds of bundles.
While cross-compilation for iOS-derived devices is possible and Meson successfully generates standalone binaries, I have not found a straightforward way to create a framework bundle (e.g., bundling Info.plist, public headers, and the binary into a .framework artifact).
This functionality is available by setting properties in build configurations of various build systems, such as CMake. However, I have not seen anything similar in Meson, nor do I know if it's planned for future implementation.
system parameters
meson --version
- Meson 1.7.0ninja --version
if it's a Ninja build - -The text was updated successfully, but these errors were encountered: