On 10/8/2023 3:06 pm, Sebastian Huber wrote:
> On 10.08.23 03:13, Chris Johns wrote:
>>
>> On 9/8/2023 7:12 pm, Sebastian Huber wrote:
>>> On 09.08.23 11:10, Cedric Berger wrote:
On 09.08.23 10:51, Sebastian Huber wrote:
> We could add some text to the option description:
>
> # Def
On 10.08.23 03:13, Chris Johns wrote:
On 9/8/2023 7:12 pm, Sebastian Huber wrote:
On 09.08.23 11:10, Cedric Berger wrote:
On 09.08.23 10:51, Sebastian Huber wrote:
We could add some text to the option description:
# Defines the program prefix of tools (compiler, assembler, linker).
# This op
On 9/8/2023 7:12 pm, Sebastian Huber wrote:
> On 09.08.23 11:10, Cedric Berger wrote:
>> On 09.08.23 10:51, Sebastian Huber wrote:
>>> We could add some text to the option description:
>>>
>>> # Defines the program prefix of tools (compiler, assembler, linker).
>>> # This option may be used to b
On 09.08.23 11:10, Cedric Berger wrote:
On 09.08.23 10:51, Sebastian Huber wrote:
We could add some text to the option description:
# Defines the program prefix of tools (compiler, assembler, linker).
# This option may be used to build RTEMS with a vendor tool suite.
# Please note that using to
On 09.08.23 10:51, Sebastian Huber wrote:
We could add some text to the option description:
# Defines the program prefix of tools (compiler, assembler, linker).
# This option may be used to build RTEMS with a vendor tool suite.
# Please note that using tool suites not provided by the RTEMS Pro
On 09.08.23 03:26, Chris Johns wrote:
On 8/8/2023 11:14 pm, Sebastian Huber wrote:
On 08.08.23 08:06, Chris Johns wrote:
n 7/8/2023 4:06 pm, Sebastian Huber wrote:
On 07.08.23 00:25, Chris Johns wrote:
On 4/8/2023 4:39 pm, Sebastian Huber wrote:
On 04.08.23 08:22, Chris Johns wrote:
On 4/8/
On 8/8/2023 11:14 pm, Sebastian Huber wrote:
> On 08.08.23 08:06, Chris Johns wrote:
>> n 7/8/2023 4:06 pm, Sebastian Huber wrote:
>>> On 07.08.23 00:25, Chris Johns wrote:
On 4/8/2023 4:39 pm, Sebastian Huber wrote:
> On 04.08.23 08:22, Chris Johns wrote:
>> On 4/8/2023 3:16 pm, Sebas
On 08.08.23 08:06, Chris Johns wrote:
n 7/8/2023 4:06 pm, Sebastian Huber wrote:
On 07.08.23 00:25, Chris Johns wrote:
On 4/8/2023 4:39 pm, Sebastian Huber wrote:
On 04.08.23 08:22, Chris Johns wrote:
On 4/8/2023 3:16 pm, Sebastian Huber wrote:
On 04.08.23 00:27, Chris Johns wrote:
On 2/8/2
On 7/8/2023 4:06 pm, Sebastian Huber wrote:
> On 07.08.23 00:25, Chris Johns wrote:
>> On 4/8/2023 4:39 pm, Sebastian Huber wrote:
>>> On 04.08.23 08:22, Chris Johns wrote:
On 4/8/2023 3:16 pm, Sebastian Huber wrote:
> On 04.08.23 00:27, Chris Johns wrote:
>> On 2/8/2023 6:49 pm, Chr
On 07.08.23 00:25, Chris Johns wrote:
On 4/8/2023 4:39 pm, Sebastian Huber wrote:
On 04.08.23 08:22, Chris Johns wrote:
On 4/8/2023 3:16 pm, Sebastian Huber wrote:
On 04.08.23 00:27, Chris Johns wrote:
On 2/8/2023 6:49 pm, Chris Johns wrote:
> I am concerned about the compatibility to the
On 4/8/2023 4:39 pm, Sebastian Huber wrote:
> On 04.08.23 08:22, Chris Johns wrote:
>> On 4/8/2023 3:16 pm, Sebastian Huber wrote:
>>> On 04.08.23 00:27, Chris Johns wrote:
On 2/8/2023 6:49 pm, Chris Johns wrote:
> I am concerned about the compatibility to the ecosystem we have. Have
On 04.08.23 08:22, Chris Johns wrote:
On 4/8/2023 3:16 pm, Sebastian Huber wrote:
On 04.08.23 00:27, Chris Johns wrote:
On 2/8/2023 6:49 pm, Chris Johns wrote:
> I am concerned about the compatibility to the ecosystem we have. Have you
built
all the tests in the testsuite with this value se
On 4/8/2023 3:16 pm, Sebastian Huber wrote:
> On 04.08.23 00:27, Chris Johns wrote:
>> On 2/8/2023 6:49 pm, Chris Johns wrote:
>> > I am concerned about the compatibility to the ecosystem we have. Have you
>> built
>>> all the tests in the testsuite with this value set to something that is not
>>
On 04.08.23 00:27, Chris Johns wrote:
On 2/8/2023 6:49 pm, Chris Johns wrote:
> I am concerned about the compatibility to the ecosystem we have. Have you
built
all the tests in the testsuite with this value set to something that is not
RTEMS default? I think a few things will break because of
On 2/8/2023 6:49 pm, Chris Johns wrote:
> I am concerned about the compatibility to the ecosystem we have. Have you
> built
> all the tests in the testsuite with this value set to something that is not
> RTEMS default? I think a few things will break because of hard coding in them.
I have asked
On 02.08.23 13:53, Karel Gardas wrote:
A bit off-topic.
On 8/2/23 10:39, Sebastian Huber wrote:
Yes, but this would be another patch and it is a bit more work since
you have to test the clang support.
Is building with clang already supported? I'm curious since this is
something I'd like to t
A bit off-topic.
On 8/2/23 10:39, Sebastian Huber wrote:
Yes, but this would be another patch and it is a bit more work since you
have to test the clang support.
Is building with clang already supported? I'm curious since this is
something I'd like to test locally too but neither code nor t
On 2/8/2023 6:56 pm, Sebastian Huber wrote:
> On 02.08.23 10:50, Chris Johns wrote:
>> On 2/8/2023 6:39 pm, Sebastian Huber wrote:
>>> On 02.08.23 10:33, Chris Johns wrote:
> diff --git a/spec/build/bsps/makeinc.yml b/spec/build/bsps/makeinc.yml
> index ac395f2f02..08fc75a8b9 100644
> -
On 02.08.23 10:50, Chris Johns wrote:
On 2/8/2023 6:39 pm, Sebastian Huber wrote:
On 02.08.23 10:33, Chris Johns wrote:
diff --git a/spec/build/bsps/makeinc.yml b/spec/build/bsps/makeinc.yml
index ac395f2f02..08fc75a8b9 100644
--- a/spec/build/bsps/makeinc.yml
+++ b/spec/build/bsps/makeinc.ym
On 2/8/2023 6:39 pm, Sebastian Huber wrote:
> On 02.08.23 10:33, Chris Johns wrote:
>>> diff --git a/spec/build/bsps/makeinc.yml b/spec/build/bsps/makeinc.yml
>>> index ac395f2f02..08fc75a8b9 100644
>>> --- a/spec/build/bsps/makeinc.yml
>>> +++ b/spec/build/bsps/makeinc.yml
>>> @@ -16,14 +16,14 @@
On 2/8/2023 6:42 pm, Sebastian Huber wrote:
> On 02.08.23 10:40, Chris Johns wrote:
>> On 2/8/2023 6:33 pm, Chris Johns wrote:
>>> On 2/8/2023 3:49 pm, Sebastian Huber wrote:
Replace --rtems-version with a PROGRAM_PREFIX option. This allows also
the use of vendor tools.> ---
>> One furth
On 02.08.23 10:40, Chris Johns wrote:
On 2/8/2023 6:33 pm, Chris Johns wrote:
On 2/8/2023 3:49 pm, Sebastian Huber wrote:
Replace --rtems-version with a PROGRAM_PREFIX option. This allows also
the use of vendor tools.> ---
One further thing to consider is if PROGRAM_PREFIX could clash with so
On 2/8/2023 6:33 pm, Chris Johns wrote:
> On 2/8/2023 3:49 pm, Sebastian Huber wrote:
>> Replace --rtems-version with a PROGRAM_PREFIX option. This allows also
>> the use of vendor tools.> ---
One further thing to consider is if PROGRAM_PREFIX could clash with something
else in a user's environme
On 02.08.23 10:33, Chris Johns wrote:
diff --git a/spec/build/bsps/makeinc.yml b/spec/build/bsps/makeinc.yml
index ac395f2f02..08fc75a8b9 100644
--- a/spec/build/bsps/makeinc.yml
+++ b/spec/build/bsps/makeinc.yml
@@ -16,14 +16,14 @@ content: |
prefix = ${PREFIX}
exec_prefix = $${prefix}
On 2/8/2023 3:49 pm, Sebastian Huber wrote:
> Replace --rtems-version with a PROGRAM_PREFIX option. This allows also
> the use of vendor tools.> ---
> spec/build/bsps/makeinc.yml| 16
> spec/build/bsps/maketarget.yml | 22 +++---
> spec/build/b
Replace --rtems-version with a PROGRAM_PREFIX option. This allows also
the use of vendor tools.
---
spec/build/bsps/makeinc.yml| 16
spec/build/bsps/maketarget.yml | 22 +++---
spec/build/bsps/optobjcopy.yml | 2 +-
spec/build/cpukit/c
26 matches
Mail list logo
