Skip to content

Enable static linking and system malloc for htool on gBMC#210

Open
wltu wants to merge 1 commit intogoogle:mainfrom
wltu:gbmc-build
Open

Enable static linking and system malloc for htool on gBMC#210
wltu wants to merge 1 commit intogoogle:mainfrom
wltu:gbmc-build

Conversation

@wltu
Copy link
Contributor

@wltu wltu commented Feb 17, 2026

Configure the htool build target to use fully static linking and system malloc when building gBMC platforms.

Configure the htool build target to use fully static linking and system malloc
when building gBMC platforms.

Signed-off-by: Willy Tu <wltu@google.com>
"htool_usb.h",
],
features = select({
"//third_party/bazel_platforms/os:linux-gbmc": ["fully_static_link"],
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if these targets are helpful externally.

@xorptr
Copy link
Collaborator

xorptr commented Feb 19, 2026

I think static linking can be achieved by passing additional arguments in the build command as well. I usually use bazel build --dynamic_mode=off --linkopt='-static' //examples:htool for building a static version of htool. I am not sure if adding this in the BUILD file is strictly necessary.

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.

2 participants