public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] CIP / Yocto / RaspberryPI 3
Date: Fri, 15 Feb 2019 10:00:55 +0100	[thread overview]
Message-ID: <33703379.pJGxf1flb9@linux-3zh6> (raw)
In-Reply-To: <OSAPR01MB3763DF2A613F037BD48E7B4CD0600@OSAPR01MB3763.jpnprd01.prod.outlook.com>

Hi Daniel,

El viernes, 15 de febrero de 2019 3:14:06 (CET) daniel.sangorrin at toshiba.co.jp 
escribi?:
> Hello Scott,
> 
> > From: cip-dev-bounces at lists.cip-project.org
> > <cip-dev-bounces@lists.cip-project.org> On Behalf Of
> > scottk at optimcloud.com
> > is there a recent CIP layer for Yocto ? We would like to test a build for
> > raspberrypi3
> CIP core is focused on making sure that Debian source code packages that are
> relevant for civil infrastructure systems are maintained for a long time.
> The tool that you use to build that source code doesn't matter.
> 
> Having said that, we do provide a few examples of how to use Debian source
> code in a yocto/OE-like project. You can find the examples here:
> https://gitlab.com/cip-project/cip-core/deby/tree/master/poky
> 
<snip>

is this the kind of information we can consolidate on the wiki at this point?

Best Regards

-- 
Agust?n Benito Bethencourt
Principal Consultant
Codethink Ltd
We respect your privacy.   See https://www.codethink.co.uk/privacy.html

  reply	other threads:[~2019-02-15  9:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15  1:15 [cip-dev] CIP / Yocto / RaspberryPI 3 scottk at optimcloud.com
2019-02-15  2:14 ` daniel.sangorrin at toshiba.co.jp
2019-02-15  9:00   ` Agustin Benito Bethencourt [this message]
2019-02-18  5:47     ` daniel.sangorrin at toshiba.co.jp
2019-02-18  8:44       ` Agustin Benito Bethencourt

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=33703379.pJGxf1flb9@linux-3zh6 \
    --to=agustin.benito@codethink.co.uk \
    --cc=cip-dev@lists.cip-project.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