public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Cc: "Lv, Liang (NSB - CN/Hangzhou)" <liang.lv@nokia-sbell.com>
Subject: Re: transplant uboot-tool(mkenvimage) to cygwin
Date: Sat, 11 Dec 2021 23:31:51 -0700	[thread overview]
Message-ID: <91147532-663c-de8b-4c51-0c3bce05aea9@SystematicSw.ab.ca> (raw)
In-Reply-To: <4d0378ec96d84645a0ee5cf976eacd7d@nokia-sbell.com>

On 2021-07-02 03:37, Lv, Liang (NSB - CN/Hangzhou) wrote:
> I find Cygwin don't support uboot-tool(mkenvimage) when I want to 
> transplant the tool, which is used to make image for flash by
> python, from linux to windows.
> But when I compile the source of uboot-tool from github, there are 
> many strange questions.
> What's the appropriate way to transplant the command to Cygwin?

It's a board and device support package which depends on board and 
device specific features and files including kernels, device trees, root 
file systems, and firmware in specific locations so can not be built in 
the Cygwin POSIX environment without adaptation:

"The development of U-Boot is closely related to Linux: some parts of
the source code originate in the Linux source tree, we have some
header files in common, and special provision has been made to
support booting of Linux images."

You could look at using a Linux emulator like WSL or VM like VirtualBox.

You may wish to look at RTEMS and other OSes which use newlib (in common 
with Cygwin) to develop similar systems.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

           reply	other threads:[~2021-12-12  6:31 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <4d0378ec96d84645a0ee5cf976eacd7d@nokia-sbell.com>]

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=91147532-663c-de8b-4c51-0c3bce05aea9@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.com \
    --cc=liang.lv@nokia-sbell.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).