All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: meta-freescale@yoctoproject.org
Subject: Re: Native package building
Date: Tue, 12 Nov 2013 09:52:58 -0700	[thread overview]
Message-ID: <52825CEA.4020401@mlbassoc.com> (raw)
In-Reply-To: <665fcc507acf439ea64bb3ddd99e7b05@BLUPR04MB023.namprd04.prod.outlook.com>

On 2013-11-12 09:43, Alberto Liberal de los Rios wrote:
> Thanks Octavio,
>
> But I have not clear my main question yet, although you maybe have answered it to me. Do you know why is it needed to add BBCLASSEXTEND = "native nativesdk" in ZLIB recipe? I am using the arm poky toolchain outside bitbake to build the library (generated with bitbake meta-toolchain), and it builds without any problem. Why is it needed to generate a native version of the ZLIB?

The act of having BBCLASSEXTEND="native" doesn't build zlib-native by itself.
The zlib-native [pseudo] recipe will be built because many other recipes need
native zlib support, e.g. building GCC needs zlib-native.

> -----Mensaje original-----
> De: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] En nombre de Otavio Salvador
> Enviado el: martes, 12 de noviembre de 2013 17:28
> Para: Alberto Liberal de los Rios
> CC: meta-freescale@yoctoproject.org
> Asunto: Re: RE: [meta-freescale] Native package building
>
> On Tue, Nov 12, 2013 at 2:19 PM, Alberto Liberal de los Rios <aliberal@arroweurope.com> wrote:
>> Thanks Octavio,
>>
>> I checked removing BBCLASSEXTEND = "native nativesdk" and adding
>> "inherit autotools" but I got an error, the reason can be the next
>>
>>
>> "About ZLIB, by looking at the configure script, we see that this
>> configure script has not been generated by autoconf (otherwise it would contain a sentence like Generated by GNU Autoconf 2.62).
>> Moreover, the project doesn't use automake since there are no
>> Makefile.am files. So zlib uses a custom build system, not a build system based on the classical autotools"
>
> Makes sense but it is unfortunate.
>
>> Anyway I don´t understand yet why it is needed to add BBCLASSEXTEND = "native nativesdk" in ZLIB and why it is not working removing it from the recipe. Could you give more details about the meaning of "when no class-<virtual> variant is provided, the defaults are used"
>
> When bitbake sees the extend, it generates a new recipe which uses the tasks as the same provided by the original .bb file. When it has a 'class-nativesdk' override of a task, this one is used, the same is valid for class-native.
>
> You can grep 'class-nativesdk' in Poky/OE-Core for some examples of this.
>

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  parent reply	other threads:[~2013-11-12 16:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 16:43 Native package building Alberto Liberal de los Rios
2013-11-12 16:49 ` Otavio Salvador
2013-11-12 16:54   ` Alberto Liberal de los Rios
2013-11-12 16:52 ` Gary Thomas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-11-12 17:01 Alberto Liberal de los Rios
2013-11-12 17:21 ` Gary Thomas
2013-11-12 17:54   ` Alberto Liberal de los Rios
2013-11-12 16:19 Alberto Liberal de los Rios
2013-11-12 16:28 ` Otavio Salvador
2013-11-12 14:38 Alberto Liberal de los Rios
2013-11-12 15:56 ` Otavio Salvador

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52825CEA.4020401@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=meta-freescale@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.