From: Michael Enright <mike@kmcardiff.com>
To: "Goswami-EXT,
Himanshu" <himanshu.goswami-EXT@continental-corporation.com>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Generating Linux Compatible binaries
Date: Fri, 3 Dec 2021 11:34:02 -0800 [thread overview]
Message-ID: <CAOC2fq82nf11UnH-4gnjjxR4oY=nrQBwFMpv+z8wjW+dcAt-CA@mail.gmail.com> (raw)
In-Reply-To: <DBBPR03MB7116FECFBA323D95B70A8BC39B6A9@DBBPR03MB7116.eurprd03.prod.outlook.com>
On Fri, Dec 3, 2021 at 8:51 AM Goswami-EXT, Himanshu
<himanshu.goswami-EXT@continental-corporation.com> wrote:
>
> Hi,
>
> I want to generate the Linux compatible binaries on Windows System.
> Cygwin is a cross compiler which offers POSIX environment.
> But I could not find any Unix libraries to generate the Linux compatible binaries.
> Could you please advice any steps that I can follow?
>
Eliot Moss recommends a VM and that's a good option.
Another option is to use Cygwin to host a cross compiler. I have used
Cygwin to build and install cross compilers that ran on Cygwin and
built code for my Raspberry Pi 2. There are many tutorials on building
and creating cross compilers and I won't try to equal them. But this
is a versatile method. If the target Linux was one that runs on a
different processor and a virtual machine would be inefficient or lack
the resources to carry out the build, then running a cross compiler on
your Windows machine, under Cygwin or otherwise, might be an option to
consider.
next prev parent reply other threads:[~2021-12-03 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 16:50 Goswami-EXT, Himanshu
2021-12-03 17:02 ` Eliot Moss
2021-12-03 19:34 ` Michael Enright [this message]
2021-12-03 20:56 ` Achim Gratz
2021-12-03 21:25 ` Eliot Moss
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='CAOC2fq82nf11UnH-4gnjjxR4oY=nrQBwFMpv+z8wjW+dcAt-CA@mail.gmail.com' \
--to=mike@kmcardiff.com \
--cc=cygwin@cygwin.com \
--cc=himanshu.goswami-EXT@continental-corporation.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).