application tutorial

[Denis Obrezkov]

Thank you for your answer.
I've already build a cross-compiler and rtems. And sample applications work.

I want to note that it is pretty easy to build rtems with rsb. But it is
also a bit confusing, because, for example, when we build an embedded linux
distribution (with buildbot or without it), we know exactly where binaries
and headers from linux kernel and libc located (because we specified it).
So, it is easy to create a new application. It is much harder with with an
unknown for many people RSB build system and complicated autotools files.

It seems, that I found binary and headers location - they are obviously in
a build directory (shame for me). And now I can understand the makefile of
an example application. But I still can't understand two things:
Where is a newlib binary?

I see code in the hello world example's makefile:
$(PGM): $(OBJS)
    $(make-exe)
could you explain where is the rule for $(OBJS) and what is $(make-exe)?

Sorry, for such stupid questions, but there are so much different .cfg,
.am, .in, waf, configure files, that it is very hard to understand what is
happening.

2017-01-03 3:07 GMT+02:00 Alan Cudmore <alan.cudmore at gmail.com>:

> Hi Denis,
>
> The simplest application is the RTEMS hello example.
> https://git.rtems.org/rtems/tree/testsuites/samples/hello
>
> Typically you use the RTEMS source builder tool ( RSB ) to build and
> install an RTEMS cross compiler. Next, you download, configure, build, and
> install the RTEMS kernel. Finally you would build your own application
> outside of the RTEMS source tree and link to the RTEMS library and startup
> code to create a standalone executable that is loaded to the target.
>
> There are some getting started docs here to help setup a cross compiler
> and build the RTEMS source with examples:
> https://devel.rtems.org/wiki/TBR/UserManual/Quick_Start
> (Not sure if that is the latest, but I believe the “sis” BSP has been
> removed. I use the sparc/erc32 BSP in it’s place)
>
> If you want to move on from the samples and build your own application
> outside of the RTEMS tree, I have a sample application framework here:
> https://github.com/alanc98/rki
>
> This gives you an example of how to create a simple RTEMS application with
> a RAM disk, shell and some sample commands to run on the shell. The
> wafscript or Makefile link in the necessary libraries for the chosen BSP.
> You can use this with RTEMS 4.11 and 4.12 ( git head ).
>
> It’s pretty easy to build for the sparc erc32 BSP and run with the
> sparc-rtems4.11-run command line simulator.
>
> To build, I use the “waf” build tool ( waf.io ). When you build for erc32
> for example, the executable program will be in :
> rki/build/sparc-rtems4.11-erc32/rki.elf
> rki.elf is the final executable that is loaded into the simulator.
>
> Hope this helps,
> Alan
>
> On Jan 2, 2017, at 8:54 AM, Denis Obrezkov <denisobrezkov at gmail.com>
> wrote:
>
> Hello, can you point me to some manual how to create a simple application
> with rtems?
> I read a lot of your tutorials like POSIX  tutorial, C Guide, Ada guide,
> Dev. environment guide, but I can't find out how to create a simple
> application.
>
> I found that I am not alone:
> http://rtems-users.rtems.narkive.com/rQP1z7Pg/rtems-application-tutorial
> http://stackoverflow.com/questions/23794870/rtems-how-
> to-compile-and-execute-programs
>
> I saw examples for rtems, but I have other questions, for example:
> Where should I place my source code? Should I place it inside of a rtems
> tree?
> How should I organize my development environment? For example, I want to
> make an application for a host computer, make myself sure that it works,
> and then cross-compile it for a target board.
> What is the structure of an rtems binary? is it something like a
> "newlib.a+rtems_kernel.a+userapplication.a".img?
>
>
>
> --
> Regards, Denis Obrezkov
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users
>
>
>


-- 
Regards, Denis Obrezkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20170103/abdc9897/attachment-0002.html>