Hi to all,
in my recipe I want to change owner and permission of a file, so I wrote:
do_install() {
ls -la ${D}/opt/user
chown -R user ${D}/opt/user
chgrp -R user ${D}/opt/user
ls -la ${D}/opt/user
chmod 754 ${D}/opt/user/user.sh
ls -la
Hi Davide,
On Tuesday 15 October 2013 12:02:20 Davide Soldan wrote:
in my recipe I want to change owner and permission of a file, so I wrote:
do_install() {
ls -la ${D}/opt/user
chown -R user ${D}/opt/user
chgrp -R user ${D}/opt/user
ls -la ${D}/opt/user
In data martedì 15 ottobre 2013 11:38:21, Paul Eggleton ha scritto:
Hi Davide,
On Tuesday 15 October 2013 12:02:20 Davide Soldan wrote:
in my recipe I want to change owner and permission of a file, so I wrote:
do_install() {
ls -la ${D}/opt/user
chown -R user
(WARNING: this post contains an unavoidable marketing component, but
i'm more interested in feedback on what i want to try as a whole new
way to teach OE/yoctoproject. and so, to work.)
over the last while, i've taught a small number of OE/yocto courses
to some commercial clients, and i've
On Tuesday 15 October 2013 18:12:42 Davide Soldan wrote:
In data martedì 15 ottobre 2013 11:38:21, Paul Eggleton ha scritto:
On Tuesday 15 October 2013 12:02:20 Davide Soldan wrote:
in my recipe I want to change owner and permission of a file, so I
wrote:
do_install() {
Hi,
can someone please give me an example of fetching the code from perforce?
I want to map files from perforce and put them in a different tree
structure in the workspace before compiling it. I also need to set user and
password.
I failed to find an example online and I don't understand the
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
Hi Chunrong,
[Re: [yocto] [Meta-security][PATCH V3 1/3] snort : add recipe] On 13.10.10 (Thu
08:19) Guo Chunrong-B40290 wrote:
Hello, all
Please give me some comments.
The meta-security maintainer and I have discussed this at length and
we're in agreement that for the time being it's
Folks,
I created the following bbapend recipe for linux-mainline_3.8.bb (from
meta-beagleboard on dylan branch) for beaglebone.
meta-mine/recipes-kernel/linux/linux-mainline_3.8.bbappend:
FILESEXTRAPATHS_prepend := ${THISDIR}/files:
SRC_URI += file://0019-mine.patch \
Hi Diego,
I may be wrong here, but I had a similar issue and I gave up. As I
understand from
https://www.yoctoproject.org/sites/yoctoproject.org/files/elc2013-kernel-lab.pdf
if you are not using the linux-yocto kernel you need the whole defconfig.
Anyway, reading the kernel lab is probably a good
Diego,
You are appending a kernel recipe that uses the Linux Yocto tooling. The
defconfig is essentially comprised of many different pieces from the meta
branch of the Yocto kernel repository and optional configuration fragments
that you provide. This tooling will not recognize a defconfig file
On Tuesday 15 October 2013 17:18:35 Paul Eggleton wrote:
On Tuesday 15 October 2013 18:12:42 Davide Soldan wrote:
In data martedì 15 ottobre 2013 11:38:21, Paul Eggleton ha scritto:
On Tuesday 15 October 2013 12:02:20 Davide Soldan wrote:
in my recipe I want to change owner and
Hi,
I guess you're setting a wrong FILESEXTRAPATHS_prepend := ${THISDIR}/files:
See this example, using simple defconfig for some devices and an
experimental configuration (WIP ;) fo others using fragments.
Attendees:
Nitin, Cristian, AlexG, Matthew, Paul, ScottR, Saul, TomZ, JeffP, Richard,
Jessica, Ross, Mark, MichaelH, Beth, Denys, Darren, Song
Agenda:
* Opens collection - 5 min (Song)
* Yocto 1.5 status - 10 min (Song/team)
https://wiki.yoctoproject.org/charts/combo.html
Hi Katu,
On Tuesday 15 October 2013 20:52:15 Katu Txakur wrote:
can someone please give me an example of fetching the code from perforce?
I want to map files from perforce and put them in a different tree
structure in the workspace before compiling it. I also need to set user and
password.
I
15 matches
Mail list logo