The toolchains are expected to be either in the PATH of the operating system or defined by the OS environment variable "RVCT_TOOLS_PATH". This patch requires the patch "0002-BaseTools-Return-an-empty-string-if-an-OS-envionment.patch" sent with the email "BaseTools: Return an empty string if an OS environment variable is not defined" to get it works. Please find in the attached patch support for RVCT and RVCTLINUX toolchains. To: Add new RVCT and RVCTLINUX toolchains (tools_def.template) 0003-BaseTools-Conf-Add-support-for-ARM-GCC-Linux-EABI-to.patch: BaseTools/Conf: Add support for ARM GCC Linux EABI toolchain This generic 'RVCT' toolchain is compatible with RVCT 3.1, 4.0, 4.1 and 5.0. 0002-BaseTools-tools_: BaseTools/tools_def.template: Replace RVCT31 toolchains by Generic RVCT toolchains 0001-BaseTools-tools_def.template-Use-GCC_ALL_CC_FLAGS-fo.patch: BaseTools/tools_def.template: Use GCC_ALL_CC_FLAGS for ARMGCC and Clean up flags Subject: RE: Add new RVCT and RVCTLINUX toolchains (tools_def.template)Ĭould you forget the patch attached to the email below that has been pending for the last 8 months.Īnd could you consider the three new attached patches: ![]() Will be processed soon.įrom: Olivier Martin Friday, Septem4:43 PM
0 Comments
Leave a Reply. |