[Bug 394] misc. RTEMS Makefile issues

bugzilla-daemon at rtems.org bugzilla-daemon at rtems.org
Tue Aug 5 17:16:51 UTC 2008


http://www.rtems.org/bugzilla/show_bug.cgi?id=394


Joel Sherrill <joel.sherrill at oarcorp.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |joel.sherrill at oarcorp.com
             Status|ASSIGNED                    |RESOLVED
           Platform|                            |All
         Resolution|                            |WONTFIX
   Target Milestone|---                         |4.9


These patches addresses the following issues:

 - all make/custom/<bsp>.cfg files should consistently 
   include 'default.cfg' _after_ defining RTEMS_CPU and 
   RTEMS_BSP_FAMILY, respectively so these variables can
   subsequently be used in 'include()' directives.

What is the bug you are trying to fix?

IMO, this patch is bogus:

* default.cfg is supposed to set up the defaults. Nothing inside of default.cfg is supposed to be overriden from other *.cfgs. 

* *.cfgs are supposed to be able to include other *.cfg recursively, to avoid code duplication. 
=> There is no need to include default.cfg in all <bsp.cfg>.



 - install libnetapps.a as a separate library, unbundled  
   from librtemsbsp.a - the netapps severely pollute
   global name space.

 - install partial libraries in addition to librtemsbsp
   and librtemscpu

These two issues are separate topics, I am filing separate PRs on them. 

 - final 'gcc-target-default.cfg' should add LD_PATHS to
   the LDFLAGS

Yet another different topic, I am refiling a new PR.

NOTE: the 'make/custom/<bsp>.cfg' patch is a separate
file.

Release:
RTEMS-4.6.0pre2

--- Comment #1 from Joel Sherrill <joel.sherrill at oarcorp.com>  2008-08-05 12:16:51 ---
This has to be obsolete by now.


-- 
Configure bugmail: http://www.rtems.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



More information about the bugs mailing list