On 01/11/2019 18:43, Gedare Bloom wrote:
On Fri, Nov 1, 2019 at 3:16 AM Hesham Almatary
<hesham.almat...@cl.cam.ac.uk> wrote:
On Thu, 31 Oct 2019 at 08:52, Sebastian Huber
<sebastian.hu...@embedded-brains.de> wrote:
On 29/10/2019 10:34, Hesham Almatary wrote:
This is to hide the new BSPs from GCC builds when building
all RISC-V BSPs with configure --target=riscv-rtems5
Can you still build the clang variants after this change?
No. That's just a temporary fix to be able to build all riscv BSPs
with until we have a better solution to conditionally add Clang flags.
Is it worth it to try to integrate support better in configure to
search for the ccfg files when clang is specified?
I think it is a waste of time to get this working properly in the old
build system.
It was a good timing that the clang patches showed up along with my work
on the new build system. I rearranged some things to make the compiler
configurable (work in progress). The user should be able to select the
compiler per BSP variant, e.g. build BSP A with GCC and BSP B with
clang. For example (bsps.ini):
[sparc/erc32]
COMPILER = gcc
[riscv/rv32imac]
COMPILER = clang
To support this, I moved the GCC compiler setup to a build specification
item:
https://git.rtems.org/sebh/rtems.git/tree/spec/build/cpukit/RTEMS-BUILD-CPUKIT-GCC.yml?h=build
All the build specification items have an "enabled-by" attribute. This
way we can enable/disable compiler flags based on the GCC/clangs selection.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
