openembedded-core.git/meta/recipes-devtools/gcc/gcc-package-runtime.inc, branch 2011-1 Mirror of openembedded-core gcc-runtime: fix installed but unpackaged files 2011-07-08T15:20:43+00:00 Nitin A Kamble nitin.a.kamble@intel.com 2011-07-07T16:34:59+00:00 e29a8601c7b028696527c70aa0d4862157ce2d81 gcc recipes has changed, currently ${PV} is 4.6 and ${BINV} is 4.6.1 version. Fix these QA warnings. WARNING: For recipe gcc-runtime, the following files were installed but not shipped in any package: WARNING: /usr/share/gcc-4.6.1/python/libstdcxx/__init__.py WARNING: /usr/share/gcc-4.6.1/python/libstdcxx/v6/__init__.py WARNING: /usr/share/gcc-4.6.1/python/libstdcxx/v6/printers.py Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> 
gcc recipes has changed, currently ${PV} is 4.6 and ${BINV} is 4.6.1 version.

Fix these QA warnings.
WARNING: For recipe gcc-runtime, the following files were installed but not shipped in any package:
WARNING:   /usr/share/gcc-4.6.1/python/libstdcxx/__init__.py
WARNING:   /usr/share/gcc-4.6.1/python/libstdcxx/v6/__init__.py
WARNING:   /usr/share/gcc-4.6.1/python/libstdcxx/v6/printers.py

Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
gcc-runtime: Fix dbg files 2011-03-11T02:16:07+00:00 Mark Hatle mark.hatle@windriver.com 2011-03-10T23:52:20+00:00 285fbd8a206eee061e27f37430499fcbe1e7284d In order to debug certain C++ items, you need the helper python components. These components should live in the -dbg package, ensure they are added to the recipe. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> 
In order to debug certain C++ items, you need the helper python
components.  These components should live in the -dbg package, ensure
they are added to the recipe.

Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
gcc-runtime: Ensure that gcc-runtime builds a debug package 2011-03-11T01:10:50+00:00 Mark Hatle mark.hatle@windriver.com 2011-03-09T00:50:02+00:00 724137e50762f190438e8e87d3f0f9edd99ea11d The gcc-runtime package will now create the proper dbg package. The RRECOMMENDS change is required to deal with the default. This is documented in bug 824. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> 
The gcc-runtime package will now create the proper dbg package.  The
RRECOMMENDS change is required to deal with the default.  This is
documented in bug 824.

Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
libgcc: use the new recipe (rather than gcc-runtime) to install libgcc_s.so* and crt*.o 2011-01-17T22:04:50+00:00 Dexuan Cui dexuan.cui@intel.com 2011-01-15T10:47:50+00:00 0df3c481309e89b93e8a57773eb9c470b4dd13a7 Currently gcc-runtime installs the files, but actually gcc-runtime's do_configure checks if the files are available, so before we build gcc-runtime, we should have some recipe install the files first! -- currently gcc-cross-intermediate actually does that(gcc-cross also installs the files, but it installs into the gcc-build-internal* directory), but gcc-cross-intermediate will have its own sysroot in future, after that, gcc-runtime won't build. So let us add this new target recipe and move the installation of the files from gcc-runtime into it. Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> 
Currently gcc-runtime installs the files, but actually gcc-runtime's
do_configure checks if the files are available, so before we build gcc-runtime,
we should have some recipe install the files first! -- currently
gcc-cross-intermediate actually does that(gcc-cross also installs the files,
but it installs into the gcc-build-internal* directory), but
gcc-cross-intermediate will have its own sysroot in future, after that,
gcc-runtime won't build. So let us add this new target recipe and move the
installation of the files from gcc-runtime into it.

Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
Major layout change to the packages directory 2010-08-27T14:29:45+00:00 Richard Purdie rpurdie@linux.intel.com 2010-08-27T14:14:24+00:00 29d6678fd546377459ef75cf54abeef5b969b5cf Having one monolithic packages directory makes it hard to find things and is generally overwhelming. This commit splits it into several logical sections roughly based on function, recipes.txt gives more information about the classifications used. The opportunity is also used to switch from "packages" to "recipes" as used in OpenEmbedded as the term "packages" can be confusing to people and has many different meanings. Not all recipes have been classified yet, this is just a first pass at separating things out. Some packages are moved to meta-extras as they're no longer actively used or maintained. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com> 
Having one monolithic packages directory makes it hard to find things
and is generally overwhelming. This commit splits it into several
logical sections roughly based on function, recipes.txt gives more
information about the classifications used.

The opportunity is also used to switch from "packages" to "recipes"
as used in OpenEmbedded as the term "packages" can be confusing to
people and has many different meanings.

Not all recipes have been classified yet, this is just a first pass
at separating things out. Some packages are moved to meta-extras as
they're no longer actively used or maintained.

Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>