Skip to content

Pass nm and objcopy as optional environment variables to build_wrapper #448

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

GuyGoldenberg
Copy link

@GuyGoldenberg GuyGoldenberg commented Apr 7, 2025

When cross-compiling Hyperscan with fat runtime enabled, the build system previously defaulted to the native objcopy and nm tools. This could lead to architecture mismatches, since the native tools might not match the target architecture produced by the cross-compiler.

This PR introduces an enhancement that allows users to specify alternative objcopy and nm executables by passing them as environment variables (OBJCOPY_PATH and NM_PATH). With these variables, the build system uses the toolchain-specific versions of these utilities, ensuring that symbol renaming is performed correctly for the target architecture.

@GuyGoldenberg GuyGoldenberg changed the title Pass nm and objcopy as optional environment variables to build_wrapper Pass nm and objcopy as optional environment variables to build_wrapper Apr 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant