All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: Marlon Smith <marlon.smith10@gmail.com>, yocto@yoctoproject.org
Subject: Re: Why use Yocto?
Date: Mon, 09 Jun 2014 16:11:24 -0700	[thread overview]
Message-ID: <53963F1C.6040608@balister.org> (raw)
In-Reply-To: <1402354370.9385.9.camel@marlon-Z68X-UD3H-B3>

On 06/09/2014 03:52 PM, Marlon Smith wrote:
> Hi everyone,
> 
> I'm developing a product that will run on a custom i.MX6 board and I'm
> trying to decide whether to use Yocto or Ubuntu (there's a version of
> Ubuntu packaged for the Wandboard that will run on our board).  The
> board will run our own custom app, and we'll modify the Linux kernel to
> support our hardware.
> 
> Ubuntu seems like it would be ready to go - just put it on an SD card,
> boot the board, compile the app and create a new SD card image from the
> result to use for manufacturing.
> 
> Yocto seems like it would be easier to remove unneeded packages from,
> and easier to cross-compile the application for.  This means we could
> have a smaller SD card image in the end.
> 
> What are your thoughts on this?

How would you handle GPL compliance with Ubuntu? The Yocto project helps
you track all the sources (and their licenses), patches and build
scripts used to create your images. This data is critical for true GPL
compliance.

Philip


> 
> Thanks
> 
> Marlon
> 
> 
> 


  reply	other threads:[~2014-06-09 23:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09 22:52 Why use Yocto? Marlon Smith
2014-06-09 23:11 ` Philip Balister [this message]
2014-06-10 10:37 ` Paul Barker
2014-06-10 11:25   ` Christian Ege
2014-06-10 14:39     ` Bob Cochran
2014-06-10 15:42       ` Nicolas Dechesne
2014-06-10 16:50         ` Marlon Smith
2014-06-10 17:16           ` Alex J Lennon
2014-06-17 20:17             ` Insop Song
2014-06-10 14:47 ` Maxim Radugin

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=53963F1C.6040608@balister.org \
    --to=philip@balister.org \
    --cc=marlon.smith10@gmail.com \
    --cc=yocto@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.