Objcopy executable path not found? about bazel-embedded HOT 3 CLOSED

Hmm, I mustn't have defined the path for objcopy. So this is definitely a bug. However, I'd recommend using this workaround for now.

Here is how I use bazel-embedded to generate separate elfs/binaries.

The way that I do things is just to use the elf, or if I need the raw binary I just use the stripped target e.g. If I have the following build definition;

cc_binary(
    name = "main",
    srcs = ["main.cc"],
)

To get the elf file I run something like this (it won't have the .elf extension unless you name the cc_binary 'main.elf');
bazel build //:main --platforms=@bazel_embedded//platforms:cortex_m4_fpu

However, if I want the binary file I use the stripped sub-target which is configured to strip all ELF sections leaving the binary e.g.

bazel build //:main.stripped --platforms=@bazel_embedded//platforms:cortex_m4_fpu

You can use strip or objcopy to achieve the same result in this case.

from bazel-embedded.

I think the main concern is keeping the build and debug symbols in the same step. If the binary is generated in a separate build step than the elf, there may be issues when going to debug via gdb. I'd rather have this copy step. I think fixing the definition here is probably the right way to do it. I'll see if I can submit a fix.

from bazel-embedded.

Yeah technically they are preserved e.g. it already looks like elf->stripped. So if you go elf(with embedded debug dwarf section)->stripped it'll still produce the same binary minus the elf headers and dwarf sections. But in any case that PR looks fine, and is fixing what I would consider a bug.

from bazel-embedded.