Re: New Build System Status

On 12/9/20 5:35 am, Joel Sherrill wrote: > On Fri, Sep 11, 2020 at 2:00 PM Gedare Bloom > wrote: > > On Fri, Sep 11, 2020 at 12:03 PM Sebastian Huber > > wrote: > > > > On 11/09/2020 17:46, Gedare Bloom wrote

Re: New Build System Status

On Fri, Sep 11, 2020 at 2:00 PM Gedare Bloom wrote: > On Fri, Sep 11, 2020 at 12:03 PM Sebastian Huber > wrote: > > > > On 11/09/2020 17:46, Gedare Bloom wrote: > > > > > I have nothing pending. I think we should switch early next week, sort > > > out any bugs during the week? > > This sounds go

Re: New Build System Status

On Fri, Sep 11, 2020 at 12:03 PM Sebastian Huber wrote: > > On 11/09/2020 17:46, Gedare Bloom wrote: > > > I have nothing pending. I think we should switch early next week, sort > > out any bugs during the week? > This sounds good. I can do some final tests builds over the week end and > then push

Re: New Build System Status

On 11/09/2020 17:46, Gedare Bloom wrote: I have nothing pending. I think we should switch early next week, sort out any bugs during the week? This sounds good. I can do some final tests builds over the week end and then push it on Monday morning. ___

Re: New Build System Status

I have nothing pending. I think we should switch early next week, sort out any bugs during the week? On Fri, Sep 11, 2020 at 4:52 AM Christian Mauderer wrote: > > On 11/09/2020 09:19, Chris Johns wrote: > > On 11/9/20 5:14 pm, Sebastian Huber wrote: > >> are there any remaining issues which preve

Re: New Build System Status

On 11/09/2020 09:19, Chris Johns wrote: > On 11/9/20 5:14 pm, Sebastian Huber wrote: >> are there any remaining issues which prevent the new build system from being >> integrated? At the moment I just sit idle and wait. If there are technical >> issues, I can fix them only if I know them. > > I ha

Re: New Build System Status

On 11/9/20 5:14 pm, Sebastian Huber wrote: > are there any remaining issues which prevent the new build system from being > integrated? At the moment I just sit idle and wait. If there are technical > issues, I can fix them only if I know them. I have none. > I have a BSP using the new build syst

Re: New Build System Status

Hello, On 16/07/2020 17:16, Sebastian Huber wrote: Hello, I sent the documentation of the new build system some days ago and at least Gedare Bloom reviewed it. https://ftp.rtems.org/pub/rtems/people/sebh/user.pdf https://ftp.rtems.org/pub/rtems/people/sebh/eng.pdf I rebased the build syste

Re: New Build System Status

Hello, I did some more tests with the latest toolchain. The ARM fenv issues are now fixed. I updated the build-2 branch to reference the latest master: https://git.rtems.org/sebh/rtems.git/log/?h=build-2 All BSPs build all tests with the following configurations: 1. [arch/bsp] RTEMS_NETWORK

Re: New Build System Status

Whenever you want to merge it and fix problems reported by lazy developers who haven't used it yet (count me in!) is fine by me. This is the "major" activity of RTEMS-6, so it will be good to integrate it and get everyone using it sooner than later. On Thu, Jul 16, 2020 at 9:16 AM Sebastian Huber

New Build System Status

Hello, I sent the documentation of the new build system some days ago and at least Gedare Bloom reviewed it. https://ftp.rtems.org/pub/rtems/people/sebh/user.pdf https://ftp.rtems.org/pub/rtems/people/sebh/eng.pdf I rebased the build system branch to the current master and squashed all comm

Re: New Build System Status

On 04/12/2019 05:11, Chris Johns wrote: On 3/12/19 5:16 pm, Sebastian Huber wrote: On 02/12/2019 23:24, Chris Johns wrote: On 2/12/19 5:42 pm, Sebastian Huber wrote: On 01/12/2019 23:53, Chris Johns wrote: On 27/11/19 11:26 pm, Sebastian Huber wrote: On 27/11/2019 13:17, Hesham Almatary wrot

Re: New Build System Status

On 3/12/19 5:16 pm, Sebastian Huber wrote: > On 02/12/2019 23:24, Chris Johns wrote: >> On 2/12/19 5:42 pm, Sebastian Huber wrote: >>> On 01/12/2019 23:53, Chris Johns wrote: On 27/11/19 11:26 pm, Sebastian Huber wrote: > On 27/11/2019 13:17, Hesham Almatary wrote: >> On Wed, 27 Nov 20

Re: New Build System Status

On 02/12/2019 23:24, Chris Johns wrote: On 2/12/19 5:42 pm, Sebastian Huber wrote: On 01/12/2019 23:53, Chris Johns wrote: On 27/11/19 11:26 pm, Sebastian Huber wrote: On 27/11/2019 13:17, Hesham Almatary wrote: On Wed, 27 Nov 2019 at 11:59, Sebastian Huber wrote: On 27/11/2019 12:49, He

Re: New Build System Status

On 2/12/19 5:42 pm, Sebastian Huber wrote: > On 01/12/2019 23:53, Chris Johns wrote: >> On 27/11/19 11:26 pm, Sebastian Huber wrote: >>> On 27/11/2019 13:17, Hesham Almatary wrote: On Wed, 27 Nov 2019 at 11:59, Sebastian Huber wrote: > On 27/11/2019 12:49, Hesham Almatary wrote:

Re: New Build System Status

On 01/12/2019 23:53, Chris Johns wrote: On 27/11/19 11:26 pm, Sebastian Huber wrote: On 27/11/2019 13:17, Hesham Almatary wrote: On Wed, 27 Nov 2019 at 11:59, Sebastian Huber wrote: On 27/11/2019 12:49, Hesham Almatary wrote: Hi Sebastian, Thanks for that great effort. I'd aim to use this b

Re: New Build System Status

On 27/11/19 11:26 pm, Sebastian Huber wrote: > On 27/11/2019 13:17, Hesham Almatary wrote: >> On Wed, 27 Nov 2019 at 11:59, Sebastian Huber >> wrote: >>> On 27/11/2019 12:49, Hesham Almatary wrote: Hi Sebastian, Thanks for that great effort. I'd aim to use this build system for my >

Re: New Build System Status

I've just figured it out myself by reading the full email from Sebastian, I clone the rtems from git://git.rtems.org/sebh/rtems.git not the official repo and waf is included. > On 29/11/2019, at 3:57 PM, yorda wrote: > > Hi Sebastian, > Thanks for updating the documentation file, I’m tryi

Re: New Build System Status

Hi Sebastian, Thanks for updating the documentation file, I’m trying to following the guide on user.pdf. Everything went well on building the toolchain, but then when I was trying to build a BSP, I could’t find waf on the rtems repo folder. So I download the latest waf from official website and

Re: New Build System Status

On 27/11/2019 14:42, Joel Sherrill wrote: On Wed, Nov 27, 2019 at 7:11 AM Hesham Almatary mailto:hesham.almat...@cl.cam.ac.uk>> wrote: On Wed, 27 Nov 2019 at 12:53, Sebastian Huber mailto:sebastian.hu...@embedded-brains.de>> wrote: > > On 27/11/2019 13:26, Sebastian Huber w

Re: New Build System Status

On Wed, Nov 27, 2019 at 6:26 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 27/11/2019 13:17, Hesham Almatary wrote: > > On Wed, 27 Nov 2019 at 11:59, Sebastian Huber > > wrote: > >> > >> On 27/11/2019 12:49, Hesham Almatary wrote: > >>> Hi Sebastian, > >>> > >>> Thanks for

Re: New Build System Status

On Wed, 27 Nov 2019 at 12:53, Sebastian Huber wrote: > > On 27/11/2019 13:26, Sebastian Huber wrote: > >> > * Can't find any "*.exe" after a default build: > >>> > >>> Ok, this is a bug, you should find the samples. > >>> > >> Is it reproducible? > > > > I will have a look at this later. > >

Re: New Build System Status

On 27/11/2019 13:26, Sebastian Huber wrote: * Can't find  any "*.exe" after a default build: Ok, this is a bug, you should find the samples. Is it reproducible? I will have a look at this later. Sorry for the confusion. This is intentional, by default no tests are built. Should I chang

Re: New Build System Status

On 27/11/2019 13:17, Hesham Almatary wrote: On Wed, 27 Nov 2019 at 11:59, Sebastian Huber wrote: On 27/11/2019 12:49, Hesham Almatary wrote: Hi Sebastian, Thanks for that great effort. I'd aim to use this build system for my RISC-V development. I followed the user manual trying to build RIS

Re: New Build System Status

On Wed, 27 Nov 2019 at 11:59, Sebastian Huber wrote: > > On 27/11/2019 12:49, Hesham Almatary wrote: > > Hi Sebastian, > > > > Thanks for that great effort. I'd aim to use this build system for my > > RISC-V development. > > > > I followed the user manual trying to build RISC-V targets and RTEMS >

Re: New Build System Status

On 27/11/2019 12:49, Hesham Almatary wrote: Hi Sebastian, Thanks for that great effort. I'd aim to use this build system for my RISC-V development. I followed the user manual trying to build RISC-V targets and RTEMS (aaf7f8b84) and here are a few comments: * .waf bsp_defaults doesn't give an e

Re: New Build System Status

Hi Sebastian, Thanks for that great effort. I'd aim to use this build system for my RISC-V development. I followed the user manual trying to build RISC-V targets and RTEMS (aaf7f8b84) and here are a few comments: * .waf bsp_defaults doesn't give an error when mistyping the BSP name, but just out

Re: New Build System Status

On 27/11/2019 00:59, Chris Johns wrote: On 27/11/19 2:07 am, Sebastian Huber wrote: I updated the build system documentation. Thank you. Thanks for having a look at it and the very helpful comments. It is now sufficiently good to get integrated from my point of view. Excellent and well

Re: New Build System Status

On 27/11/19 2:07 am, Sebastian Huber wrote: > I updated the build system documentation. Thank you. > It is now sufficiently good to get integrated from my point of view. Excellent and well done. However it cannot be merged until the question I raised here is resolved ... https://lists.rtems.org

Re: New Build System Status

Hello, I updated the build system documentation. It is now sufficiently good to get integrated from my point of view. https://ftp.rtems.org/pub/rtems/people/sebh/eng.pdf https://ftp.rtems.org/pub/rtems/people/sebh/user.pdf -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-

Re: New Build System Status

On 26/11/2019 02:11, Chris Johns wrote: I am saying I have no system to prove it right now. I think it is still needed but can't reproduce it. I don't like removing it quietly without a replacement to detect and report something to a user that X occurred, please report so we know what hosts this

Re: New Build System Status

On 26/11/19 11:55 am, Joel Sherrill wrote: > On Mon, Nov 25, 2019, 6:30 PM Chris Johns > wrote: > On 26/11/19 10:46 am, Joel Sherrill wrote: > > On Mon, Nov 25, 2019 at 5:28 PM Chris Johns > >

Re: New Build System Status

On Mon, Nov 25, 2019, 6:30 PM Chris Johns wrote: > On 26/11/19 10:46 am, Joel Sherrill wrote: > > On Mon, Nov 25, 2019 at 5:28 PM Chris Johns > > wrote: > > On 26/11/19 9:57 am, Joel Sherrill wrote: > > > On Mon, Nov 25, 2019 at 3:19 PM Chris Johns >

Re: New Build System Status

On 26/11/19 10:46 am, Joel Sherrill wrote: > On Mon, Nov 25, 2019 at 5:28 PM Chris Johns > wrote: > On 26/11/19 9:57 am, Joel Sherrill wrote: > > On Mon, Nov 25, 2019 at 3:19 PM Chris Johns > >

Re: New Build System Status

On Mon, Nov 25, 2019 at 5:28 PM Chris Johns wrote: > On 26/11/19 9:57 am, Joel Sherrill wrote: > > On Mon, Nov 25, 2019 at 3:19 PM Chris Johns > > wrote: > > > > On 26/11/19 8:05 am, Joel Sherrill wrote: > > > On Mon, Nov 25, 2019 at 2:12 AM Sebastian Huber > >

Re: New Build System Status

On 26/11/19 9:57 am, Joel Sherrill wrote: > On Mon, Nov 25, 2019 at 3:19 PM Chris Johns > wrote: > > On 26/11/19 8:05 am, Joel Sherrill wrote: > > On Mon, Nov 25, 2019 at 2:12 AM Sebastian Huber > > >

Re: New Build System Status

On Mon, Nov 25, 2019 at 3:19 PM Chris Johns wrote: > On 26/11/19 8:05 am, Joel Sherrill wrote: > > On Mon, Nov 25, 2019 at 2:12 AM Sebastian Huber > > sebastian.hu...@embedded-brains.de>> > > wrote: > > > > On 25/11/2019 08:55, Chris Johns wrote: > > > > > > On 25/11/19 5:28 pm, Seba

Re: New Build System Status

On 26/11/19 8:05 am, Joel Sherrill wrote: > On Mon, Nov 25, 2019 at 2:12 AM Sebastian Huber > > > wrote: > > On 25/11/2019 08:55, Chris Johns wrote: > > > > On 25/11/19 5:28 pm, Sebastian Huber wrote: > >> > >> On 24/11/2019 23:25, Ch

Re: New Build System Status

On Mon, Nov 25, 2019 at 2:12 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 25/11/2019 08:55, Chris Johns wrote: > > > > On 25/11/19 5:28 pm, Sebastian Huber wrote: > >> > >> On 24/11/2019 23:25, Chris Johns wrote: > > Should there be a note or something about waf needing

Re: New Build System Status

On 25/11/2019 08:55, Chris Johns wrote: On 25/11/19 5:28 pm, Sebastian Huber wrote: On 24/11/2019 23:25, Chris Johns wrote: Should there be a note or something about waf needing python and we recommend python3? Plus waf needs a `python` installed and not just `python2` or `python3`? I think

Re: New Build System Status

On 25/11/19 5:28 pm, Sebastian Huber wrote: > > > On 24/11/2019 23:25, Chris Johns wrote: Should there be a note or something about waf needing python and we recommend python3? Plus waf needs a `python` installed and not just `python2` or `python3`? >>> I think this belongs

Re: New Build System Status

On 24/11/2019 23:25, Chris Johns wrote: Should there be a note or something about waf needing python and we recommend python3? Plus waf needs a `python` installed and not just `python2` or `python3`? I think this belongs to the Host Computer section. The quick start uses the RSB, so if you ma

Re: New Build System Status

On 23/11/19 9:15 pm, Sebastian Huber wrote: > - Am 22. Nov 2019 um 23:31 schrieb Chris Johns chr...@rtems.org: > >> On 23/11/19 1:49 am, Sebastian Huber wrote: >>> Hello, >>> >>> I converted all BSPs to the new build system. I was able to build the tests >>> for >>> all BSPs without POSIX and

Re: New Build System Status

- Am 22. Nov 2019 um 23:31 schrieb Chris Johns chr...@rtems.org: > On 23/11/19 1:49 am, Sebastian Huber wrote: >> Hello, >> >> I converted all BSPs to the new build system. I was able to build the tests >> for >> all BSPs without POSIX and networking (my system was busy for approx. 8h). I >>

Re: New Build System Status

On 23/11/19 1:49 am, Sebastian Huber wrote: > Hello, > > I converted all BSPs to the new build system. I was able to build the tests > for > all BSPs without POSIX and networking (my system was busy for approx. 8h). I > will do build runs with POSIX and networking enabled next week. Nice and wel

Re: New Build System Status

Hello, I converted all BSPs to the new build system. I was able to build the tests for all BSPs without POSIX and networking (my system was busy for approx. 8h). I will do build runs with POSIX and networking enabled next week. I think the build system structure is quite good. With the scrip

Re: New Build System Status

> On Nov 15, 2019, at 10:05 , Sebastian Huber > wrote: > > Hello, > > I nearly finished the conversion script for the BSPs. I can now configure 194 > BSP variants with the default BSP option values. Some BSPs need modifications > by hand, e.g. linker command files and special boot files. T

New Build System Status

Hello, I nearly finished the conversion script for the BSPs. I can now configure 194 BSP variants with the default BSP option values. Some BSPs need modifications by hand, e.g. linker command files and special boot files. There are now about 2000 YAML files. It needs about 11 seconds to build