All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burton, Ross" <ross.burton@intel.com>
To: "Rajasekaran, Monica" <Monica.Rajasekaran@us.fujitsu.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Installing openvswitch
Date: Thu, 9 Jun 2016 23:11:59 +0100	[thread overview]
Message-ID: <CAJTo0LZo1G5p3As9NbdTdW=W4rvpCS8quu3sR_OgW7mT729hjw@mail.gmail.com> (raw)
In-Reply-To: <111ACD726EC3464BAED310F5EA7BEBDA5FDCA9@RCHEXMBP1.fnc.net.local>

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

On 9 June 2016 at 22:40, Rajasekaran, Monica <
Monica.Rajasekaran@us.fujitsu.com> wrote:

> I have openvswitch package installed in my image. But, I do not see a
> folder called “openvswitch-2.xx” with all the source code at all! I need
> the code to make changes. I see these:
>
>
You installed binary packages, not the sources.

If you want to edit and compile openvswitch on the target then just fetch
it using git and edit/compile/install using gcc and so on (adding tools-sdk
to IMAGE_FEATURES will give you a full toolchain to get this started).

Alternatively you can use devtool to edit on your build machine and deploy
updated binaries to your target.  The Development Manual covers this,
http://www.yoctoproject.org/docs/2.1/dev-manual/dev-manual.html#devtool-use-devtool-modify-to-enable-work-on-code-associated-with-an-existing-recipe
.

Ross

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

      reply	other threads:[~2016-06-09 22:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 15:13 Installing openvswitch Rajasekaran, Monica
2016-06-09 15:48 ` Burton, Ross
2016-06-09 18:56   ` Rajasekaran, Monica
2016-06-09 19:47     ` Burton, Ross
2016-06-09 19:53       ` Rajasekaran, Monica
2016-06-09 20:57         ` Rajasekaran, Monica
2016-06-09 21:40           ` Rajasekaran, Monica
2016-06-09 22:11             ` Burton, Ross [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='CAJTo0LZo1G5p3As9NbdTdW=W4rvpCS8quu3sR_OgW7mT729hjw@mail.gmail.com' \
    --to=ross.burton@intel.com \
    --cc=Monica.Rajasekaran@us.fujitsu.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.