STM32F4 discovery makefile

[Gedare Bloom]

You can see an example of using plain Makefile in
http://git.rtems.org/examples-v2/ I think this repo uses the
"RTEMS_MAKEFILE_PATH" environment variable.

You can use autotools for your application if you think the complexity
is needed. For a simple application, copying the example Makefiles
should work well enough. You should verify you can build the
examples-v2 samples and run them before you try your custom code.

I think just using Makefile is going to be simpler to follow. You
should start by getting the examples working.

-Gedare

On Tue, Oct 29, 2013 at 10:07 PM, sarraciro <sarraciro at yahoo.it> wrote:
> Hi,
> in this days I studied about autotools.... for try to understand how to
> build a RTEMS  application for STM32F4-Discovery out of the RTEMS tree.
> Supposing that the location of the structure reside in
> $(HOME)/rtems/apps,
> a minimal structure like this:
> apps/template$:cd testprjct && tree -L 2 .
> testprjct
> |--m4
> |--builddir
> |--Makefile.am
> |--configure.ac
> |--src
> |   |--Makefile.am
> |   |--init.c
> |   |--inc
> |        |-- system.h
> |--lib
> |   |--Makefile.am
> |   |--minefiles.c
> |   |--minefiles.h
> |--README
>
> 1.  It is sufficient in your opinion to guarantee the correct building
> process of the template?
> 2. This approach (by autotools) is the "suggested way" or the best way
> is continuing to try with classic (write by hand) Makefile? I  thought
> that the autotools approach could be interesting?
>
> I don't have a strong know-how in software-engineering thus I think the
> simpler approach is the more suitable for me.
>
> Regards
>
> --
> RC
>
> Il giorno sab, 26/10/2013 alle 19.39 +0200, sarraciro ha scritto:
>> Yes, Later I noticed that I've already saw it... (in git repository...
>> in fact.. :) ).
>> I've created the directories structure in the home directory!
>> First I want to learn to build  a RTEMS application.
>> Regards
>>
>> --
>> SC
>>
>>
>> Il giorno sab, 26/10/2013 alle 15.49 +0200, Sebastian Huber ha scritto:
>> > On 10/25/2013 09:21 PM, sarraciro wrote:
>> > > Hi, I've built with success a template for the stm32f4-discovery.
>> > > Now I want integrate the GPIO support (for starting) .
>> > > I've noticed :
>> > > http://git.rtems.org/rtems/tree/c/src/lib/libbsp/arm/stm32f4
>> >
>> > This is the BSP source directory for the STM32 Cortex-M controllers.
>> >
>> > >
>> > > Then I made this structure: two directories inc & src
>> > > |-- init.c
>> > > |-- lib
>> > > |   |-- inc
>> > > |   |   |-- bsp.h
>> > > |   |   |-- bspopts.h
>> > > |   |   |-- i2c.h
>> > > |   |   |-- io.h
>> > > |   |   |-- irq.h
>> > > |   |   |-- rcc.h
>> > > |   |   |-- stm32f4.h
>> > > |   |   |-- stm32f4xxxx_gpio.h
>> > > |   |   |-- stm32f4xxxx_rcc.h
>> > > |   |   |-- stm32_i2c.h
>> > > |   |   |-- stm32_usart.h
>> > > |   |   `-- usart.h
>> > > |   |-- Makefile
>> > > |   `-- src
>> > > |       |-- console-config.c
>> > > |       |-- i2c.c
>> > > |       |-- i2c-config.c
>> > > |       `-- usart.c
>> > > |-- Makefile
>> > > |-- pmacros.h
>> > > |-- system.h
>> > > |-- init.c
>> > > |-- lib
>> > > |   |-- inc
>> > > |   |   |-- bsp.h
>> > > |   |   |-- bspopts.h
>> > > |   |   |-- i2c.h
>> > > |   |   |-- io.h
>> > > |   |   |-- irq.h
>> > > |   |   |-- rcc.h
>> > > |   |   |-- stm32f4.h
>> > > |   |   |-- stm32f4xxxx_gpio.h
>> > > |   |   |-- stm32f4xxxx_rcc.h
>> > > |   |   |-- stm32_i2c.h
>> > > |   |   |-- stm32_usart.h
>> > > |   |   `-- usart.h
>> > > |   |-- Makefile
>> > > |   `-- src
>> > > |       |-- console-config.c
>> > > |       |-- i2c.c
>> > > |       |-- i2c-config.c
>> > > |       `-- usart.c
>> > > |-- Makefile
>> > > |-- pmacros.h
>> > > |-- system.h
>> > >
>> > > but how to  the control of building-process can flow through from the
>> > > first makefile to the second one (lib/) for build the library? there 're
>> > > any recommendations to build & include a library?
>> >
>> > Where do you have this directory layout?  Do you want to develop a RTEMS
>> > application or do you want to enhance the BSP?
>> >
>>
>>
>> _______________________________________________
>> rtems-users mailing list
>> rtems-users at rtems.org
>> http://www.rtems.org/mailman/listinfo/rtems-users
>
>
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-users