How to add a directory in rtems-src?

Fri Nov 7 12:32:18 UTC 2014

How

On November 4, 2014 9:34:21 PM CST, "黄喜" <huangxi_hans at 163.com> wrote:
>
>
>Hello  Joel ,
>
>        Very lucky send a mail to you.
>
>I download the RTEMS4.11 source code from git and compile it Ok for
>BeagleBoneBlack port. And then, I want to write the application code, I
>want to create a directory 'application ' in rtems-src directory, and
>put some directory in or .h or .c files in  application directory. It
>maybe modify some Makefiles or configure files, So I want to know the
>details to tell me how to do it. Thank you very much.

You need to ask this on the users@ or devel@ mailing list. 

In general, the examples-v2 repo shows how to make an application exe using simple Makefiles or WAF (nicer) as the build system. But the Beagle has steps past that to get the exe into the right format and onto bootable media.

Best to discuss this on list.

>
>       Best Regards.
>
>
>                   Hans.
>
>
>
>
>
>
>
>
>At 2014-11-03 18:00:26, users-request at rtems.org wrote: >Send users
>mailing list submissions to >	users at rtems.org > >To subscribe or
>unsubscribe via the World Wide Web, visit
>>	http://lists.rtems.org/mailman/listinfo/users >or, via email, send a
>message with subject or body 'help' to >	users-request at rtems.org > >You
>can reach the person managing the list at >	users-owner at rtems.org >
>>When replying, please edit your Subject line so it is more specific
>>than "Re: Contents of users digest..." > > >Today's Topics: > > 1. Re:
>Re: The error in building rtems source about stm32f4 bsp >
>(ZhangZhenxing) > 2. RTEMS Run-time Linker vs Linux dynamic linking
>with shared > library. (Thomas Kim) > >
>>----------------------------------------------------------------------
>> >Message: 1 >Date: Thu, 30 Oct 2014 22:38:15 +0800 >From:
>ZhangZhenxing <harbor0727 at gmail.com> >To: "Joel Sherrill"
><joel.sherrill at oarcorp.com>, "Chris Nott" >	<chrisn at vl.com.au>, users
><users at rtems.org> >Subject: Re: Re: The error in building rtems source
>about stm32f4 bsp >Message-ID: <201410302238127869601 at gmail.com>
>>Content-Type: text/plain; charset="utf-8" > > >On 10/29/2014 11:19 AM,
>Chris Nott wrote: >> On 29/10/2014 8:05 AM, Joel Sherrill wrote: >>>
>Sure. Hopefully Chris Nott will just reply to this thread when he >>>
>spots it. :) >> Quite correct, I missed a file. This patch should
>resolve it. >Patch is merged. > >Thanks. > >--joel >>> On 10/29/2014
>9:59 AM, ZhangZhenxing wrote: >>>> Thank you very much! >>>> can I
>receive the notice about the error if it is resolved? >>>>
>------------------------------------------------------------------------
>>>>> harbor0727 at gmail.com >>>> >>>> *From:* Joel Sherrill
><mailto:joel.sherrill at oarcorp.com> >>>> *Date:* 2014-10-29 22:40 >>>>
>*To:* ZhangZhenxing <mailto:harbor0727 at gmail.com>; users >>>>
><mailto:users at rtems.org>; Chris Nott <mailto:chrisn at vl.com.au> >>>>
>*Subject:* Re: The error in building rtems source about stm32f4 bsp
>>>>> >>>> On 10/29/2014 9:07 AM, ZhangZhenxing wrote: >>>>> Hi, >>>>> I
>got the rtems source builder by the git command("git clone >>>>>
>git://git.rtems.org/rtems-source-builder.git") and builded rtems >>>>>
>4.11 toolschain by rtems source builder with the configure >>>>>
>command("../rtems-4.10.99/configure --target=arm-rtems4.11 >>>>>
>--enable-posix --enable-networking --enable-cxx >>>>>
>--enable-rtemsbsp=stm32f4 --prefix=/opt/rtems-4.11/"). Then, when >>>>>
>executing "sudo make all install" after "./configure", there is a >>>>>
>error as follow. Why is it? How can I do for it? Thank you very >>>>>
>much! >>>>> >>>> I can confirm that I got the same message in a full
>build I ran >>>> Oct 26 but just now got a >>>> chance to look at.
>Using git blame, I see it was the last patch >>>> from Chris Nott[1].
>It looks >>>> like the patch added some files to the Makefile.am but
>didn't >>>> include them. >>>> >>>> Chris.. if you can submit a patch
>which adds the new files, I will >>>> merge it quickly. At the >>>>
>moment, no stm32f*is building. >>>> >>>>
>http://git.rtems.org/rtems/commit/?id=040ed0b4cdd1c663408664ba3a8b2e5de0cf54e0
>>>>> >>>> You could locally revert that patch and continue until it is
>>>>> resolved in the master. This is >>>> just part of using the
>development head. 99% of the time it is OK >>>> but once in a while,
>>>>> it isn't. >>>> >>>> [1] Sorry I missed having lunch or dinner with
>you. :) >>>>> make[8]: Entering directory >>>>>
>`/home/zhangzhenxing/rtems/build-rtems/arm-rtems4.11/c/stm32f4/lib/libbsp/arm/stm32f4'
>>>>>> /usr/bin/install -c -m 644 >>>>>
>../../../../../../../../rtems-source-code/c/src/lib/libbsp/arm/stm32f4/bsp_specs
>>>>>> ../../../../../.././stm32f4/lib/bsp_specs >>>>> /usr/bin/install
>-c -m 644 >>>>>
>../../../../../../../../rtems-source-code/c/src/lib/libbsp/arm/stm32f4/../../shared/include/tm27.h
>>>>>> ../../../../../.././stm32f4/lib/include/tm27.h >>>>>
>/usr/bin/install -c -m 644 >>>>>
>../../../../../../../../rtems-source-code/c/src/lib/libbsp/arm/stm32f4/include/bsp.h
>>>>>> ../../../../../.././stm32f4/lib/include/bsp.h >>>>>
>/usr/bin/install -c -m 644 >>>>>
>../../../../../../../../rtems-source-code/c/src/lib/libbsp/arm/stm32f4/../../shared/include/coverhd.h
>>>>>> ../../../../../.././stm32f4/lib/include/coverhd.h >>>>>
>/usr/bin/install -c -m 644 include/bspopts.h >>>>>
>../../../../../.././stm32f4/lib/include/bspopts.h >>>>>
>/usr/bin/install -c -m 644 >>>>>
>../../../../../../../../rtems-source-code/c/src/lib/libbsp/arm/stm32f4/../../shared/include/bootcard.h
>>>>>> ../../../../../.././stm32f4/lib/include/bsp/bootcard.h >>>>>
>/usr/bin/install -c -m 644 >>>>>
>../../../../../../../../rtems-source-code/c/src/lib/libbsp/arm/stm32f4/../../shared/include/utility.h
>>>>>> ../../../../../.././stm32f4/lib/include/bsp/utility.h >>>>>
>/usr/bin/install -c -m 644 >>>>>
>../../../../../../../../rtems-source-code/c/src/lib/libbsp/arm/stm32f4/../../shared/include/irq-generic.h
>>>>>> ../../../../../.././stm32f4/lib/include/bsp/irq-generic.h >>>>>
>/usr/bin/install -c -m 644 >>>>>
>../../../../../../../../rtems-source-code/c/src/lib/libbsp/arm/stm32f4/../../shared/include/irq-info.h
>>>>>> ../../../../../.././stm32f4/lib/include/bsp/irq-info.h >>>>>
>/usr/bin/install -c -m 644 >>>>>
>../../../../../../../../rtems-source-code/c/src/lib/libbsp/arm/stm32f4/../../shared/include/stackalloc.h
>>>>>> ../../../../../.././stm32f4/lib/include/bsp/stackalloc.h >>>>>
>/usr/bin/install -c -m 644 >>>>>
>../../../../../../../../rtems-source-code/c/src/lib/libbsp/arm/stm32f4/../shared/include/start.h
>>>>>> ../../../../../.././stm32f4/lib/include/bsp/start.h >>>>>
>/usr/bin/install -c -m 644 >>>>>
>../../../../../../../../rtems-source-code/c/src/lib/libbsp/arm/stm32f4/../shared/armv7m/include/armv7m-irq.h
>>>>>> ../../../../../.././stm32f4/lib/include/bsp/armv7m-irq.h >>>>>
>/usr/bin/install -c -m 644 >>>>>
>../../../../../../../../rtems-source-code/c/src/lib/libbsp/arm/stm32f4/include/irq.h
>>>>>> ../../../../../.././stm32f4/lib/include/bsp/irq.h >>>>>
>/usr/bin/install -c -m 644 >>>>>
>../../../../../../../../rtems-source-code/c/src/lib/libbsp/arm/stm32f4/include/usart.h
>>>>>> ../../../../../.././stm32f4/lib/include/bsp/usart.h >>>>>
>/usr/bin/install -c -m 644 >>>>>
>../../../../../../../../rtems-source-code/c/src/lib/libbsp/arm/stm32f4/include/stm32f4.h
>>>>>> ../../../../../.././stm32f4/lib/include/bsp/stm32f4.h >>>>>
>/usr/bin/install -c -m 644 >>>>>
>../../../../../../../../rtems-source-code/c/src/lib/libbsp/arm/stm32f4/include/stm32f10xxx_gpio.h
>>>>>> ../../../../../.././stm32f4/lib/include/bsp/stm32f10xxx_gpio.h
>>>>>> /usr/bin/install -c -m 644 >>>>>
>../../../../../../../../rtems-source-code/c/src/lib/libbsp/arm/stm32f4/include/stm32f10xxx_rcc.h
>>>>>> ../../../../../.././stm32f4/lib/include/bsp/stm32f10xxx_rcc.h
>>>>>> /usr/bin/install -c -m 644 >>>>>
>../../../../../../../../rtems-source-code/c/src/lib/libbsp/arm/stm32f4/include/stm32f10xxx_exti.h
>>>>>> ../../../../../.././stm32f4/lib/include/bsp/stm32f10xxx_exti.h
>>>>>> make[8]: *** No rule to make target `include/stm32f4xxxx_adc.h',
>>>>>> needed by >>>>>
>`../../../../../.././stm32f4/lib/include/bsp/stm32f4xxxx_adc.h'. >>>>>
>Stop. >>>>> make[8]: Leaving directory >>>>>
>`/home/zhangzhenxing/rtems/build-rtems/arm-rtems4.11/c/stm32f4/lib/libbsp/arm/stm32f4'
>>>>>> make[7]: *** [preinstall-recursive] Error 1 >>>>> make[7]:
>Leaving directory >>>>>
>`/home/zhangzhenxing/rtems/build-rtems/arm-rtems4.11/c/stm32f4/lib/libbsp/arm'
>>>>>> make[6]: *** [preinstall-recursive] Error 1 >>>>> make[6]:
>Leaving directory >>>>>
>`/home/zhangzhenxing/rtems/build-rtems/arm-rtems4.11/c/stm32f4/lib/libbsp'
>>>>>> make[5]: *** [preinstall-recursive] Error 1 >>>>> make[5]:
>Leaving directory >>>>>
>`/home/zhangzhenxing/rtems/build-rtems/arm-rtems4.11/c/stm32f4/lib'
>>>>>> make[4]: *** [preinstall-recursive] Error 1 >>>>> make[4]:
>Leaving directory >>>>>
>`/home/zhangzhenxing/rtems/build-rtems/arm-rtems4.11/c/stm32f4' >>>>>
>make[3]: *** [preinstall-stamp] Error 2 >>>>> make[3]: Leaving
>directory >>>>>
>`/home/zhangzhenxing/rtems/build-rtems/arm-rtems4.11/c/stm32f4' >>>>>
>make[2]: *** [all-recursive] Error 1 >>>>> make[2]: Leaving directory
>>>>>> `/home/zhangzhenxing/rtems/build-rtems/arm-rtems4.11/c/stm32f4'
>>>>>> make[1]: *** [all-recursive] Error 1 >>>>> make[1]: Leaving
>directory >>>>> `/home/zhangzhenxing/rtems/build-rtems/arm-rtems4.11/c'
>>>>>> make: *** [all-recursive] Error 1 >>>>> >>>>>
>------------------------------------------------------------------------
>>>>>> >>>>> harbor0727 at gmail.com >>>> -- Joel Sherrill, Ph.D. Director
>of Research & >>>> Development >>>> joel.sherrill at OARcorp.com On-Line
>Applications Research >>>> Ask me about RTEMS: a free RTOS Huntsville
>AL 35805 >>>> Support Available (256) 722-9985 >>>> >>> > >-- >Joel
>Sherrill, Ph.D. Director of Research & Development
>>joel.sherrill at OARcorp.com On-Line Applications Research >Ask me about
>RTEMS: a free RTOS Huntsville AL 35805 >Support Available (256)
>722-9985 > >-------------- next part -------------- >An HTML attachment
>was scrubbed... >URL:
><http://lists.rtems.org/pipermail/users/attachments/20141030/4ebcaf11/attachment-0001.html>
>> >------------------------------ > >Message: 2 >Date: Mon, 3 Nov 2014
>19:00:21 +0900 >From: Thomas Kim <thomas73.kim at gmail.com> >To:
>"rtems-users at rtems.org" <users at rtems.org> >Subject: RTEMS Run-time
>Linker vs Linux dynamic linking with shared >	library. >Message-ID:
>>	<CADY8aTBTKXBNuKrKfWSyDM2eBMq7ocLhZwBgo+43pqKb2V=2Rg at mail.gmail.com>
>>Content-Type: text/plain; charset="utf-8" > >Dear Sir, > >I checked
>that RTEMS runtime linker was updated on main tree. > >I would like to
>know something before testing RTEMS run-time linker. > >I am guessing
>that RTEMS run-time linker is different with linux dynamic >linking
>with shared library(*.so.*). > >I hope that RTEMS run-time linker is
>same concept with Linux dynamic >linking with shared library. > >Please
>advise me. > >Best Regards. >-------------- next part --------------
>>An HTML attachment was scrubbed... >URL:
><http://lists.rtems.org/pipermail/users/attachments/20141103/39e94d26/attachment.html>
>> >------------------------------ > >Subject: Digest Footer >
>>_______________________________________________ >users mailing list
>>users at rtems.org >http://lists.rtems.org/mailman/listinfo/users >
>>------------------------------ > >End of users Digest, Vol 98, Issue 1
>>************************************ 