[Bug 1758] RTEMS Makefile templates include paths screwed up

[bugzilla-daemon at rtems.org]

https://www.rtems.org/bugzilla/show_bug.cgi?id=1758

--- Comment #10 from Ralf Corsepius <ralf.corsepius at rtems.org> 2011-03-08 12:00:04 CST ---
(In reply to comment #9)
> it would help if we get an idea how an application Makefile should look like
It would follow whatever style you prefer and whatever tool you want.

> when the templates are gone. 
They won't be gone - They'd be split out of the source tree.

The major difference to now would be that they'd be generated from examination
of an installed BSP.


> I am sure you have a mechanism in mind to ensure
> the application is built with the right libraries, compiler settings etc.

Basically like you would build any other arbitrary package on any other 
arbitrary OS: From manual input, using your preferred tools, being assisted by
standardized tools (e.g. pkg-config support files).

The fundamental difference would be that you are not being forced to struggle
the fragments and don't have to fight with them (e.g. when default.cfg pulls in
gcc-target-default.cfg which will kill most configure scripts).

Let me provide an example to get you rough feeling for where I am heading to:
# make RTEMS_BSP=sis
# make install
# export PKG_CONFIG_PATH=/opt/rtems-4.11/lib/pkgconfig
# pkg-config --cflags sparc-rtems4.11-sis
-qrtems -B/opt/rtems-4.11/sparc-rtems4.11/lib/
-B/opt/rtems-4.11/sparc-rtems4.11/sis/lib/ --specs bsp_specs -mcpu=cypress -O2
-g -Wall -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs

cd <myapplication>
./configure CFLAGS=$(pkg-config --cflags sparc-rtems4.11-sis) ....

[Note: This is with a real current rtems-4.11 source tree, 
Things are broken and arguable in detail, but the basic already work]

-- 
Configure bugmail: https://www.rtems.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.