Drifting somewhat off-topic here, but were you aware of the mirror
capability of BitBake?
SOURCE_MIRROR_URL = "http://${SHARED_HOME}/oe/sources/";
INHERIT += own-mirrors
This allows the user to cache downloads on their own HDD as usual (eg.
in ${OEDIR}/downloads), but to pull downloaded tarballs from a shared
server on your corporate intranet. Of course, someone needs to put them
there in the first place.
Eliyahu Skoczylas wrote:
Another helpful thing for us was simply to save all of the downloads.
DL_DIR = "${SHARED_HOME}/sources"
That way they get downloaded once, into a common place.
We can wipe out the build tree and start over, including unpacking
relevant packages again, but the downloads get reused.
HTH,
- Eliyahu
--
Eliyahu Skoczylas +972 (54) 214-1505
While <[EMAIL PROTECTED]> is temporarily down, please use <[EMAIL PROTECTED]>,
instead.
----- Original message -----
From: "Douglas Royds" <[EMAIL PROTECTED]>
To: "Using OE" <[email protected]>
Date: Tue, 23 Sep 2008 16:49:27 +1200
Subject: Re: Checking out sources in working directory
I suggest that in a site.conf or local.conf file you set:
TMPDIR = "${OEDIR}/build/tmp"
In this way, the user can change directory into
build/tmp/work/.../packagename-version/, and simply launch bitbake from
that directory. They can carry out their full change/build/commit cycle
from the one directory.
Edward K Chien wrote:
Hi,
I'm in the process of evaluating OpenEmbedded for our project here and
have a question. For some packages, we would like to be able to
'checkout' the latest sources directly into the working dir (instead
of the typical normal unpacking phase of untaring the file). This
would be a simpler working model or our engineers where they can
directly make changes, build, and commit all from one place. In
Looking through the bitbake/OE sources, I don't see any builtin
infrastructure for that now.
I know I can easily just redefine do_checkout() and do_unpack() for my
specific packages and perform the checkouts there, but I was wondering
if there are any better ways of doing it? We are using git for our
repository and i'm thinking of letting the do_checkout() run as
normal, but redefine do_unpack so that it runs git-new-workdir from
the fetched/cloned repo into the working dir.
My question is has anyone done this for their projects and if so, any
insight?
Eddie
_______________________________________________
Openembedded-users mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users
=======================================================================
This email, including any attachments, is only for the intended
addressee. It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
altered or corrupted during transmission.
=======================================================================
_______________________________________________
Openembedded-users mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users
_______________________________________________
Openembedded-users mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users
=======================================================================
This email, including any attachments, is only for the intended
addressee. It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
altered or corrupted during transmission.
=======================================================================
_______________________________________________
Openembedded-users mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users
