From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Thu, 17 Oct 2019 10:10:40 -0400 Subject: [U-Boot] [PATCH 5/5] doc: Add documentation for how to build U-Boot host tools In-Reply-To: References: <1571243245-4991-1-git-send-email-bmeng.cn@gmail.com> <1571243245-4991-6-git-send-email-bmeng.cn@gmail.com> <20191016182046.GW16029@bill-the-cat> Message-ID: <20191017141040.GI16029@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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 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 > > > > 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. -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: