Objcopy = cc_toolchain. Might not be exactly what you are looking for, but at least better than a genrule. I've written my own 'objcopy' rule that uses 'find_cc_toolchain(ctx).cc_toolchain.objcopy_executable' to get the path to the objcopy tool from the cc_toolchain. Any advice or references would be greatly appreciated! I was able to get this to work, however, it seems like a cleaner way to do this would be to have it automatically called from the toolchain since it's defined in the tool path anyway. I install gcc-arm-none-eabi-49-2015q3-20150921-win32 make-3.81 coreutils-5.3.0 and setup the PATH in windows then i enter CMD mode make some command to make sure it works set the toolchain path in makefile.windows and makefile.posix 'C:GNU Tools ARM Embedded4. Install GCC toolchain for ARM Microcontroller. I know that a common way to do this is to use a genrule and have it call my cc_binary in the tools parameter. Features to convert an executable file into binary and hex file formats. Currently, I have a feature whose actions are associated with all of the objc ACTION_NAMES from My code builds, but it does not trigger any objcopy actions. However, I can't seem to get the implementation correct. an action that calls objcopy -o binary hello_world hello_world.bin). It looks like maybe an action_config is the right approach, and then from there I can specify a feature with flag groups that are associated with that action (i.e. bin files when I run my bazel build? At the moment, it only looks like the compiler and linker tools and associated actions get called. How do I edit my toolchain such that it automatically calls the objcopy tool and generates. In my toolchain_config.bzl file, I have the tool paths defined to include things like the gcc tool, ld tool, objcopy tool, etc. I'm building a cc_binary hello_world application with a gnu arm gcc cross compiler toolchain.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |