[OE-core] [PATCH 2/2] gcc-runtime: add SUMMARY values

[Paul Eggleton]

On Wed, 06 Jul 2016 14:03:53 Khem Raj wrote:
> On Wed, Jul 6, 2016 at 1:55 PM, Paul Eggleton
> 
> <paul.eggleton at linux.intel.com> wrote:
> > It's useful to know what the various libraries are that get produced by
> > gcc-runtime, as well as to have a specific SUMMARY for the recipe.
> > 
> > Signed-off-by: Paul Eggleton <paul.eggleton at linux.intel.com>
> > ---
> > 
> >  meta/recipes-devtools/gcc/gcc-runtime.inc | 27
> >  +++++++++++++++++++++++++++
> >  1 file changed, 27 insertions(+)
> > 
> > diff --git a/meta/recipes-devtools/gcc/gcc-runtime.inc
> > b/meta/recipes-devtools/gcc/gcc-runtime.inc index 99f50f8..8e42a57 100644
> > --- a/meta/recipes-devtools/gcc/gcc-runtime.inc
> > +++ b/meta/recipes-devtools/gcc/gcc-runtime.inc
> > @@ -1,5 +1,7 @@
> > 
> >  require gcc-configure-common.inc
> > 
> > +SUMMARY = "Runtime libraries for GCC compilers"
> > +
> > 
> >  # Over-ride the LICENSE set by gcc-${PV}.inc to remove "& GPLv3"
> >  # All gcc-runtime packages are now covered by the runtime exception.
> >  LICENSE = "GPL-3.0-with-GCC-exception"
> > 
> > @@ -135,73 +137,98 @@ FILES_${PN}-dbg += "\
> > 
> >  "
> >  
> >  FILES_libg2c = "${target_libdir}/libg2c.so.*"
> > 
> > +SUMMARY_libg2c = "Companion runtime library for g77"
> > 
> >  FILES_libg2c-dev = "\
> >  
> >      ${libdir}/libg2c.so \
> >      ${libdir}/libg2c.a \
> >      ${libdir}/libfrtbegin.a \
> >  
> >  "
> > 
> > +SUMMARY_libg2c-dev = "Companion runtime library for g77 - development
> > files"> 
> >  FILES_libstdc++ = "${libdir}/libstdc++.so.*"
> > 
> > +SUMMARY_libstdc++ = "C++ standard library for g++"
> 
> Drop for g++ here, something like GNU Standard C++ Library is better
> in general replace g++/gcc with GNU
> 
> >  FILES_libstdc++-dev = "\
> >  
> >      ${includedir}/c++/ \
> >      ${libdir}/libstdc++.so \
> >      ${libdir}/libstdc++*.la \
> >      ${libdir}/libsupc++.la \
> >  
> >  "
> > 
> > +SUMMARY_libstdc++-dev = "C++ standard library for g++ - development
> > files"
> > 
> >  FILES_libstdc++-staticdev = "\
> >  
> >      ${libdir}/libstdc++*.a \
> >      ${libdir}/libsupc++.a \
> >  
> >  "
> > 
> > +SUMMARY_libstdc++-staticdev = "C++ standard library for g++ - static
> > development files"
> same here Header files and libraries for C++ development
> 
> >  FILES_libstdc++-precompile-dev =
> >  "${includedir}/c++/${TARGET_SYS}/bits/*.gch"> 
> > +SUMMARY_libstdc++-precompile-dev = "C++ standard library from gcc -
> > precompiled header files"> 
> >  FILES_libssp = "${libdir}/libssp.so.*"
> > 
> > +SUMMARY_libssp = "Stack smashing protection library for gcc"
> 
> same here

My aim was to give some explanation as to why these things might be installed 
if a user was to find them in their image. Are these libraries used by other 
compilers?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre