From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/5] doc: Add documentation for how to build U-Boot host tools
Date: Thu, 17 Oct 2019 11:12:36 -0400 [thread overview]
Message-ID: <20191017151236.GL16029@bill-the-cat> (raw)
In-Reply-To: <CAEUhbmXApvTTfreW9eMSAYa5YoQ2hUq1_uQowPjNLYUoErDJuw@mail.gmail.com>
On Thu, Oct 17, 2019 at 11:02:47PM +0800, Bin Meng wrote:
> Hi Tom,
>
> On Thu, Oct 17, 2019 at 10:10 PM Tom Rini <trini@konsulko.com> wrote:
> >
> > On Thu, Oct 17, 2019 at 09:50:57AM +0800, Bin Meng wrote:
> > > Hi Tom,
> > >
> > > On Thu, Oct 17, 2019 at 2:20 AM Tom Rini <trini@konsulko.com> wrote:
> > > >
> > > > On Wed, Oct 16, 2019 at 09:27:25AM -0700, Bin Meng wrote:
> > > >
> > > > > This adds a reST document for how to build U-Boot host tools,
> > > > > including information for both Linux and Windows.
> > > > >
> > > > > Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
> > > >
> > > > So here's where I think things get interesting. Off the top of my head,
> > > > I think we can use the free GitLab.com-provided hosts of which there are
> > > > Windows-based ones (we would need to do some labeling of jobs so that
> > > > most things only run on our Linux hosts but one job runs on the Windows
> > > > infra). I'm less sure we can do such a matrix with Travis. But is
> > > > there some way we could get this Windows tool build into CI and thus
> > > > keep it from breaking in the future? Thanks!
> > >
> > > Yes, I would like to have GitLab CI to do the Windows build for us.
> > > However I did not find the free GitLab.com-provided hosts. Any hints?
> >
> > Yeah, OK, I was wrong. You have to be on gitlab.com and they don't have
> > Windows. And I don't know enough Windows to figure out how to automate
> > going from a Microsoft-provided free VirtualBox image to having that
> > have GitLab Runner also installed.
>
> Ah that's bad we can't find a GitLab hosted free Windows VM.
>
> So I looked at Microsoft Azure pipeline and it looks we can set up a
> free account for U-Boot.
> See https://azure.microsoft.com/en-us/blog/announcing-azure-pipelines-with-unlimited-ci-cd-minutes-for-open-source/
That's interesting. Would you mind trying to get something going with
that? Maybe long term we can use that as an alternative to travis too.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191017/67c86ab4/attachment.sig>
next prev parent reply other threads:[~2019-10-17 15:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 16:27 [U-Boot] [PATCH 0/5] tools: Support building U-Boot host tools for Windows via MSYS2 Bin Meng
2019-10-16 16:27 ` [U-Boot] [PATCH 1/5] tools: image.h: Use portable uint32_t instead of linux-specific __be32 Bin Meng
2019-10-16 16:27 ` [U-Boot] [PATCH 2/5] tools: mtk_image.h: Use portable uintXX_t instead of linux-specific __leXX Bin Meng
2019-10-16 16:27 ` [U-Boot] [PATCH 3/5] tools: zynqmpbif: Use compiler builtin instead of linux-specific __swab32 Bin Meng
2019-10-16 16:27 ` [U-Boot] [PATCH 4/5] linux/types.h: Surround 'struct ustat' with __linux__ Bin Meng
2019-10-16 16:27 ` [U-Boot] [PATCH 5/5] doc: Add documentation for how to build U-Boot host tools Bin Meng
2019-10-16 18:20 ` Tom Rini
2019-10-17 1:50 ` Bin Meng
2019-10-17 14:10 ` Tom Rini
2019-10-17 15:02 ` Bin Meng
2019-10-17 15:12 ` Tom Rini [this message]
2019-10-18 1:53 ` Bin Meng
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=20191017151236.GL16029@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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