Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

file in wrong format error #453

Open
aregtech opened this issue Nov 21, 2024 · 0 comments
Open

file in wrong format error #453

aregtech opened this issue Nov 21, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@aregtech
Copy link
Owner

Describe:

When cross-compiling and if a packages is available in the system, the compilation may fail with error message file in wrong format, indicating that CMake found a package, but the it is available for the other architecture. For example, if we compile for the target x86 on the host machine x86_64, where the sqlite3.so library / package is available and it is compiled for the x86_64 architecture, the find_package(SQLite3) will indicate that found package, but when try to link for x86 target build, it will fail.

To Reproduce
on the x86_64 host install sqlite3 library and compile for the target x86:

cmake -B ./build -DAREG_COMPILER_FAMILY=gnu -DAREG_PROCESSOR=x86
cmake --build ./build -j

Expected behavior
The build should succeed.

  • SQLite3: Try to detect the available libraries / packages for the target architecture. If not found, build from sources.
  • ncurses: Force to disable the build with extended objects if ncurses is not available for the target architecture.
  • GTest:: Force to fetch the sources and build gtest library if it is not available for the target architecture.
@aregtech aregtech added the bug Something isn't working label Nov 21, 2024
@aregtech aregtech self-assigned this Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: No status
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant