Re: libbsd development policy clarification needed?

On Fri, Feb 3, 2023 at 3:29 PM Christian Mauderer wrote: > > > > Am 3. Februar 2023 22:52:48 MEZ schrieb Gedare Bloom : > >On Fri, Feb 3, 2023 at 2:39 PM Christian Mauderer wrote: > >> > >> > >> > >> Am 3. Februar 2023 22:12:06 MEZ schrieb Gedare Bloom : > >> >On Fri, Feb 3, 2023 at 12:52 PM

Re: libbsd development policy clarification needed?

Am 3. Februar 2023 22:52:48 MEZ schrieb Gedare Bloom : >On Fri, Feb 3, 2023 at 2:39 PM Christian Mauderer wrote: >> >> >> >> Am 3. Februar 2023 22:12:06 MEZ schrieb Gedare Bloom : >> >On Fri, Feb 3, 2023 at 12:52 PM wrote: >> >> >> >> Hello Gedare, >> >> >> >> Am 03.02.23 um 19:51 schrieb

Re: libbsd development policy clarification needed?

On Fri, Feb 3, 2023 at 2:39 PM Christian Mauderer wrote: > > > > Am 3. Februar 2023 22:12:06 MEZ schrieb Gedare Bloom : > >On Fri, Feb 3, 2023 at 12:52 PM wrote: > >> > >> Hello Gedare, > >> > >> Am 03.02.23 um 19:51 schrieb Gedare Bloom: > >> > On Thu, Feb 2, 2023 at 11:24 PM Christian MAUDERER

Re: libbsd development policy clarification needed?

Am 3. Februar 2023 22:12:06 MEZ schrieb Gedare Bloom : >On Fri, Feb 3, 2023 at 12:52 PM wrote: >> >> Hello Gedare, >> >> Am 03.02.23 um 19:51 schrieb Gedare Bloom: >> > On Thu, Feb 2, 2023 at 11:24 PM Christian MAUDERER >> > wrote: >> >> >> >> Hello Karel, >> >> >> >> On 2023-02-02 12:43,

Re: libbsd development policy clarification needed?

On Fri, Feb 3, 2023 at 12:52 PM wrote: > > Hello Gedare, > > Am 03.02.23 um 19:51 schrieb Gedare Bloom: > > On Thu, Feb 2, 2023 at 11:24 PM Christian MAUDERER > > wrote: > >> > >> Hello Karel, > >> > >> On 2023-02-02 12:43, Karel Gardas wrote: > >>> > >>> Guys, > >>> > >>> recently I needed

Re: libbsd development policy clarification needed?

Hello Gedare, Am 03.02.23 um 19:51 schrieb Gedare Bloom: On Thu, Feb 2, 2023 at 11:24 PM Christian MAUDERER wrote: Hello Karel, On 2023-02-02 12:43, Karel Gardas wrote: Guys, recently I needed to work with RTEMS/NFS. As this is provided by libbsd I took this and following two

Re: [PATCH] wscript: Deduplicate installed files

It's already in a common objxilinxsupport.yml file. The problem is that it is being included by two different drivers both imported from the xilinx upstream driver repo, so it currently attempts to install those shared headers twice. I suppose the solution could be to bundle the shared code

Re: [PATCH] wscript: Deduplicate installed files

On 03.02.23 19:45, Kinsey Moore wrote: This is my first stab at solving this duplicate install problem. I could manually solve the problem by deduplicating the object includes and moving it up to the BSP, but that is less intuitive since these drivers both depend on the same code and the BSP

Re: libbsd development policy clarification needed?

On Thu, Feb 2, 2023 at 11:24 PM Christian MAUDERER wrote: > > Hello Karel, > > On 2023-02-02 12:43, Karel Gardas wrote: > > > >Guys, > > > > recently I needed to work with RTEMS/NFS. As this is provided by libbsd > > I took this and following two sentences below from master branch > >

Re: [PATCH] wscript: Deduplicate installed files

This is my first stab at solving this duplicate install problem. I could manually solve the problem by deduplicating the object includes and moving it up to the BSP, but that is less intuitive since these drivers both depend on the same code and the BSP doesn't depend on it directly. Kinsey

[PATCH] wscript: Deduplicate installed files

The addition of the NAND and NOR drivers both depending on the Xilinx support code independently has introduced the possibility of duplicate installed headers. This duplication results in multiple header install attempts which can conflict since the installs can run on multiple CPUs. This change

Re: [PATCH 1/1] Modified Hello World

Thanks, you can email a screenshot to me and j...@rtems.org. On Tue, Jan 31, 2023 at 9:24 PM Jviraj wrote: > > From: Viraj Jagadale > > --- > testsuites/samples/hello/init.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/testsuites/samples/hello/init.c