Re: AW: Naming convention for Rust target platforms

2024-01-30 Thread Sebastian Huber
On 30.01.24 13:45, jan.som...@dlr.de wrote: -Ursprüngliche Nachricht- Von: Sebastian Huber Gesendet: Dienstag, 30. Januar 2024 11:08 An: devel Cc: Sommer, Jan Betreff: Re: Naming convention for Rust target platforms Hello Jan, On 29.01.24 19:41,jan.som...@dlr.de wrote: So, for the Zyn

Re: Naming convention for Rust target platforms

2024-01-30 Thread Karel Gardas
On 1/29/24 19:41, jan.som...@dlr.de wrote: Hi everyone, As mentioned in the other Rust thread, I am working on an initial Rust port for RTEMS. The target platform for testing is the ARM Xilinx Zynq-7000 based BSPs. Where I am not completely sure, is how to name the new target for Rust (see her

Re: Naming convention for Rust target platforms

2024-01-30 Thread Karel Gardas
On 1/30/24 18:13, Frank Kühndel wrote: Which name Rust accepts instead of "armv7a-rtems6-eabihf" depends on the naming convention of the Rust community:     https://docs.rust-embedded.org/embedonomicon/custom-target.html According to this file, the part `eabi` is for bare metal. Would this be

[PATCH rtems-source-builder 1/2] source-builder: Handle modern pkg-config symlinks

2024-01-30 Thread Kinsey Moore
Modern versions of pkg-config include new architecture-specific symlinks that are sometimes checked before "pkg-config". This causes builds to detect the system pkg-config instead of the local overridden pkg-config and fail to build properly. This overrides those new symlinks to restore build funct

[PATCH rtems-source-builder 2/2] qemu: Update CFLAGS and LDFLAGS overrides

2024-01-30 Thread Kinsey Moore
QEMU used to honor LDFLAGS and CFLAGS and has since moved to accepting them via --extra-cflags and --extra-ldflags options to configure. --- source-builder/config/qemu-common-2.cfg | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source-builder/config/qemu-common-2.cfg b/so

Re: Naming convention for Rust target platforms

2024-01-30 Thread Joel Sherrill
On Tue, Jan 30, 2024 at 3:15 PM Joel Sherrill wrote: > > > On Tue, Jan 30, 2024 at 11:13 AM Frank Kühndel < > frank.kuehn...@embedded-brains.de> wrote: > >> Hello Jan, >> >> On 1/29/24 19:41, jan.som...@dlr.de wrote: >> > Hi everyone, >> > >> > As mentioned in the other Rust thread, I am working

Re: Naming convention for Rust target platforms

2024-01-30 Thread Joel Sherrill
On Tue, Jan 30, 2024 at 11:13 AM Frank Kühndel < frank.kuehn...@embedded-brains.de> wrote: > Hello Jan, > > On 1/29/24 19:41, jan.som...@dlr.de wrote: > > Hi everyone, > > > > As mentioned in the other Rust thread, I am working on an initial Rust > port for RTEMS. > > The target platform for testi

Re: Naming convention for Rust target platforms

2024-01-30 Thread Frank Kühndel
Hello Jan, On 1/29/24 19:41, jan.som...@dlr.de wrote: Hi everyone, As mentioned in the other Rust thread, I am working on an initial Rust port for RTEMS. The target platform for testing is the ARM Xilinx Zynq-7000 based BSPs. Where I am not completely sure, is how to name the new target for Ru

AW: Naming convention for Rust target platforms

2024-01-30 Thread Jan.Sommer
> -Ursprüngliche Nachricht- > Von: Sebastian Huber > Gesendet: Dienstag, 30. Januar 2024 11:08 > An: devel > Cc: Sommer, Jan > Betreff: Re: Naming convention for Rust target platforms > > Hello Jan, > > On 29.01.24 19:41, jan.som...@dlr.de wrote: > > So, for the Zynq and similar BSPs

Re: Naming convention for Rust target platforms

2024-01-30 Thread Sebastian Huber
Hello Jan, On 29.01.24 19:41, jan.som...@dlr.de wrote: So, for the Zynq and similar BSPs this would yield for the Rust target something like: armv7a-rtems6-eabihf (and possibly armv7a-rtems6-eabi). Similarly, for other ARM BSPs additional Rust targets would need to be added. Which might add up t