All of lore.kernel.org
 help / color / mirror / Atom feed
From: gary@missionsecure.com
To: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>,
	"gartnerd@gmail.com" <gartnerd@gmail.com>
Subject: Re: [yocto] devtool question/issue
Date: Sat, 6 Feb 2021 12:15:19 +0000	[thread overview]
Message-ID: <BL0PR1701MB253187BD8B139EE1B4EDCA7EC3B19@BL0PR1701MB2531.namprd17.prod.outlook.com> (raw)
In-Reply-To: <CAMVSYA7KXo9ZwkZdTiUyVmcx+m-2cVCqbH8Oy48Qi+ry_ORv6w@mail.gmail.com>

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

I always start with

devtool modify <package>

This sets-up the workspace,  puts the package source code in workspace/sources, inits git, etc.

Gary

________________________________
From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> on behalf of David Gartner via lists.yoctoproject.org <gartnerd=gmail.com@lists.yoctoproject.org>
Sent: Friday, February 5, 2021 8:06 PM
To: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org>
Subject: [yocto] devtool question/issue

Hi,

I've been following along on this youtube video created by a Yocto developer:

https://youtu.be/nqHylLP2NmA?t=1592<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyoutu.be%2FnqHylLP2NmA%3Ft%3D1592&data=04%7C01%7Cgary%40missionsecure.com%7C329a2b43d61447cffd8008d8ca3b7be6%7Cf0ca9611f13f4dc98e1b119172b8ec5d%7C0%7C0%7C637481704140380417%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=0RQV%2B6iZPxU1yiO0UZelJRYUobYziChOGr1OI41O%2BEI%3D&reserved=0>

I can reproduce everything presented until it comes to using devtool (as shown at the time index in the link given above). When attempting to run:

devtool add git://blah-blah-gitrepo

I get the error:


ERROR: workspace layer not set up

My understanding from the documentation is that the "workspace" layer gets created (if it doesn't exist) when running devtool with a command such as add.

Since I'm new at using Yocto, it's likely that I"m missing something fundamental here.

Any help/suggestions would be appreciated

Gary Huband
Sr. Software and Systems Engineer

Office: 434.284.8071 x720
Direct: 434.260.4995
Gary@MissionSecure.com

Follow Us!
LinkedIn<https://www.linkedin.com/company/mission-secure-inc->  |  Blog<https://www.missionsecure.com/blog?utm_source=email-signature&utm_medium=email&utm_campaign=blog-email-sig>  |  Website<https://www.missionsecure.com/?utm_source=email-signature&utm_medium=email&utm_campaign=web-email-sig>

: : : : : : : : : : : : : : : : : : : : : : : : : : :

[MSi]

This email and any files transmitted with it are confidential and proprietary and intended solely for the use of the individual or entity to whom they are addressed. Any dissemination, distribution or copying of this communication is strictly prohibited without our prior permission. If you received this in error, please contact the sender and delete the material from any computer.


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

  reply	other threads:[~2021-02-06 12:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-06  1:06 devtool question/issue gartnerd
2021-02-06 12:15 ` gary [this message]
2021-02-06 18:48   ` David Gartner
2021-02-07  0:57     ` David Gartner
2021-02-08  0:01       ` David Gartner
2021-02-08  8:10         ` [yocto] " Josef Holzmayr

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=BL0PR1701MB253187BD8B139EE1B4EDCA7EC3B19@BL0PR1701MB2531.namprd17.prod.outlook.com \
    --to=gary@missionsecure.com \
    --cc=gartnerd@gmail.com \
    --cc=yocto@lists.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.