All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jeremy A. Puhlman" <jpuhlman@mvista.com>
To: Michael Habibi <mikehabibi@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Best practice for building a large amount of source files
Date: Thu, 10 Dec 2015 13:32:24 -0800	[thread overview]
Message-ID: <5669EF68.40408@mvista.com> (raw)
In-Reply-To: <CAOsp8o9_bzZg5nYsPrqiCNOm+SBphZpwmY1eGqav2g2ULYCCSw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1565 bytes --]



On 12/10/2015 1:16 PM, Michael Habibi wrote:
> If I have some source I want to bring into my layer, for example:
>
> Recipe dir:
> meta-mylayer/recipes-management/myapplication/myapplication_1.0/<tons 
> of source files>
>
> What is the best option for adding all of these and compiling? As far 
> as I know, you have to do one of the following:
>
> 1) Use a fetch that fetches a tarball with all your source, or a repo 
> with all of your source
> 2) Use a million-line long SRC_URI assignment to include every file 
> that your application uses.
>
> Is there a third (or fourth) option that I may have missed?
Not necessarily best practice, but it is something that bitbake has 
supported.

If you create a directory under myapplication_1.0 that is unique and not 
an override, you can specify the directory name
as the SRC_URI and bitbake will pull the directory and its contents in.

Something like 
meta-mylayer/recipes-management/myapplication/myapplication_1.0/mysources/<tons 
of source files>

and SRC_URI file://mysources

It should work.

Something like the following:

 > find recipes/
recipes/
recipes/myapp
recipes/myapp/files
recipes/myapp/files/mysources
recipes/myapp/files/mysources/Makefile
recipes/myapp/myapp_1.0.bb
 > cat recipes/myapp/myapp_1.0.bb
LICENSE="MIT"
LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"

SRC_URI = "file://mysources"

S="${WORKDIR}/mysources"

>
> Michael
>
>
>
>

-- 
Jeremy A. Puhlman
jpuhlman@mvista.com


[-- Attachment #2: Type: text/html, Size: 3247 bytes --]

  reply	other threads:[~2015-12-10 21:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-10 21:16 Best practice for building a large amount of source files Michael Habibi
2015-12-10 21:32 ` Jeremy A. Puhlman [this message]
2015-12-10 21:54 ` Burton, Ross
2015-12-10 22:07   ` Michael Habibi
2015-12-10 22:11     ` Burton, Ross

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=5669EF68.40408@mvista.com \
    --to=jpuhlman@mvista.com \
    --cc=mikehabibi@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.