diff options
| author |   Scott Rifenbark <srifenbark@gmail.com> | 2015-10-15 10:32:40 -0700 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-10-21 23:06:35 +0100 |
| commit | cd48ccccaf0c5b62195cfed56574e6f7eb5d8ee7 (patch) | |
| tree | b5c2fdb4a65a068ab597b8efbe3aa599a273cc1c /documentation/dev-manual/dev-manual-common-tasks.xml | |
| parent | dc9e4cbfe6fc2bec4503de0b23fb4f02475c10ac (diff) | |
| download | openembedded-core-contrib-cd48ccccaf0c5b62195cfed56574e6f7eb5d8ee7.tar.gz | |
dev-manual: Added notes to clarify use of pkg-config
Fixed [YOCTO #8168]
I placed a couple notes in the "Configuration" and "Compilation"
sections within the "Writing a New Recipe" section. These notes
point out that the build system (as of release 1.7) now disables
several *-config scripts. The user should be using "pkg-config"
to ensure proper pathname construction and location of these
types of scripts.
(From yocto-docs rev: a46fd0f7b4d5da7bf3b218441ec5b9a6ef552266)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual/dev-manual-common-tasks.xml')
| -rw-r--r-- | documentation/dev-manual/dev-manual-common-tasks.xml | 24 |
1 files changed, 23 insertions, 1 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 44b046d965..5694776b88 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -2249,6 +2249,19 @@ Typically, setting these options is accomplished by running a configure script with some options, or by modifying a build configuration file. + <note> + As of Yocto Project Release 7.1, some of the core recipes + that package binary configuration scripts now disable the + scripts due to the scripts previously requiring error-prone + path substitution. + The OpenEmbedded build system uses + <filename>pkg-config</filename> now, which is much more + robust. + You can find a list of the <filename>*-config</filename> + scripts that are disabled list in the + "<ulink url='&YOCTO_DOCS_REF_URL;#migration-1.7-binary-configuration-scripts-disabled'>Binary Configuration Scripts Disabled</ulink>" + section in the Yocto Project Reference Manual. + </note> </para> <para> @@ -2364,7 +2377,16 @@ <para> However, if the compile step fails, you need to diagnose the failure. - Here are some common issues that cause failures: + Here are some common issues that cause failures. + <note> + For cases where improper paths are detected for + configuration files or for when libraries/headers cannot + be found, be sure you are using the more robust + <filename>pkg-config</filename>. + See the note in section + "<link linkend='new-recipe-configuring-the-recipe'>Configuring the Recipe</link>" + for additional information. + </note> <itemizedlist> <listitem><para><emphasis>Parallel build failures:</emphasis> These failures manifest themselves as intermittent |