-
Hi everyone, I'm working on a project where I need to cross compile and build static libraries for Magick++, MagickCore, and MagickWand for arm64, to integrate with my existing Android project. I've set up my environment variables and configured ImageMagick 7.1.1-25 for my host (aarch64-unknown-linux-android) and build (x86_64-pc-linux-gnu) systems. Here's a summary of my configuration: Shared libraries: disabled I believe this incorrect path inclusion is causing the errors, but I'm not sure how to remove or correct these auto-included x86_64 paths in the CFLAGS. Has anyone here successfully compiled fully static for ImageMagick targeting arm64 on Android if so could you please share it? I'd also greatly appreciate any guidance or suggestions especially on how to fix the CFLAGS to be appropriate for arm64. Thank you in advance for your help! Summary of configure env for reference: Host system type: aarch64-unknown-linux-android
Shared libraries --enable-shared=no no Install documentation: yes Memory allocation library: Delegate library configuration: Delegate program configuration: Font configuration: X11 configuration: Options used to compile and link: Error seen when I run 'make': |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 7 replies
-
The build has not been tested on Linux (as per the FAQ entry), so I'd try using Windows to build it first of all. Alternatively, you could get github to build it for you, or try the docker image. |
Beta Was this translation helpful? Give feedback.
-
Thank you for your response and guidance on my previous query. Following your advice, I initiated a fully static build from the ImageMagick GitHub repository. I used the --enable-static=yes option in the configure-any.sh script to ensure a static build. However, I have a question regarding the static libraries. In the binaries attached to the repository, I noticed the absence of static libraries like libmagick++, libMagicCore, or libMagicWand. I'm trying to understand whether these static libraries are indeed part of the provided binaries, and perhaps I'm just not locating them correctly. Could you please shed some light on this? Do these static libraries exist in the repo, or are they not included in the binaries for some reason? Any clarification on this would be very helpful. |
Beta Was this translation helpful? Give feedback.
-
@ramasita saw in your commits you were trying to build armeabi-v7a you can also trigger all for building all at once or the wanted core in local build/Handle release workflow's |
Beta Was this translation helpful? Give feedback.
@ramasita saw in your commits you were trying to build armeabi-v7a
i want to inform that the source now supports all cores (
arm64-v8a
|armeabi-v7a
|x86
|x86_64
)you can also trigger all for building all at once or the wanted core in local build/Handle release workflow's