Replies: 1 comment
-
In general we often cannot offer much assistance with cross-compile issues unless there's definitive proof that it's a Cmake config error on our part. Two things do jump out at me though:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello everyone,
I'm currently working on cross-compiling the AWS IoT Device SDK C++ for a Raspberry Pi Zero 2W project. I've encountered some challenges, particularly around using a custom-built OpenSSL library for the ARM architecture.
Environment:
Target Device: Raspberry Pi Zero 2W
Host System: MacOS M2 running Ubuntu 22.04 docker container
Cross-Compilation Toolchain: arm-linux-gnueabihf
AWS IoT Device SDK C++ Version: (SDK version or commit hash)
CMake Version: 3.22.1
Issue Description:
The main issue arises during the linking phase, where the SDK or one of its dependencies (specifically s2n-tls) is unable to find or correctly link against the custom-built OpenSSL (libcrypto.so.1.0.0 not found).
Despite setting the -DUSE_OPENSSL=ON flag and providing paths to the custom-built OpenSSL (using -DOPENSSL_ROOT_DIR, -DOPENSSL_CRYPTO_LIBRARY, and -DOPENSSL_SSL_LIBRARY), the build process seems to be not recognizing or correctly using the provided OpenSSL library paths.
Steps Taken:
Cross-compiled OpenSSL for ARM and installed it in a custom directory.
Attempted to cross-compile AWS IoT Device SDK C++ with the following CMake configuration:
Beta Was this translation helpful? Give feedback.
All reactions