From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: a few questions on the proper use of TEMPLATECONF
Date: Mon, 4 Aug 2014 07:19:49 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1408040716390.7019@localhost> (raw)
In-Reply-To: <alpine.LFD.2.11.1408040630210.6237@localhost>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1532 bytes --]
short followup to my earlier post ... it seems like
oe-setup-builddir doesn't do a whole lot of input validation. for fun,
i tried to define a new project using /tmp for TEMPLATECONF, knowing
there was nothing valid there to be used as sample files, and here's
what i got (in part):
cp: cannot stat ‘/tmp/local.conf.sample’: No such file or directory
You had no conf/bblayers.conf file. The configuration file has been
created for
you with some default values. To add additional metadata layers into
your
configuration please add entries to this file.
The Yocto Project has extensive documentation about OE including a
reference manual
which can be found at:
http://yoctoproject.org/documentation
For more information about OpenEmbedded see their website:
http://www.openembedded.org/
sed: can't read /tmp/bblayers.conf.sample: No such file or directory
in the end, despite the obviously fatal errors, i got a new build
directory with no local.conf, and an empty bblayers.conf. that doesn't
really match what the error messages were telling me above.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2014-08-04 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 10:54 a few questions on the proper use of TEMPLATECONF Robert P. J. Day
2014-08-04 11:19 ` Robert P. J. Day [this message]
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=alpine.LFD.2.11.1408040716390.7019@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox