From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Generating Linux Compatible binaries
Date: Fri, 03 Dec 2021 21:56:45 +0100 [thread overview]
Message-ID: <87bl1xmmpe.fsf@Rainer.invalid> (raw)
In-Reply-To: <DBBPR03MB7116FECFBA323D95B70A8BC39B6A9@DBBPR03MB7116.eurprd03.prod.outlook.com> (Himanshu Goswami-EXT's message of "Fri, 3 Dec 2021 16:50:35 +0000")
Goswami-EXT, Himanshu writes:
> I want to generate the Linux compatible binaries on Windows System.
If you are on a recent Windows version your easiest option is probably
to use WSL and use native compilation on Linux. second easiest is
likely to set up a VM to run Linux in (that might actually be easier
than WSL if you already have some virtualisation environment set up for
something else, but you said you were on Windows).
> Cygwin is a cross compiler which offers POSIX environment.
No, Cygwin is a user-space layer on top of Windows that provides a POSIX
environment for applications that target Cygwin (i.e. Cygwin
applications are neither Windows nor Linux applications).
> But I could not find any Unix libraries to generate the Linux compatible binaries.
> Could you please advice any steps that I can follow?
Just like you'd do on any other non-Linux system: set up a
cross-compilation toolchain and start compiling all dependencies until
you can finally compile whatever Linux application you wanted orginally.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
next prev parent reply other threads:[~2021-12-03 20:56 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
2021-12-03 20:56 ` Achim Gratz [this message]
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=87bl1xmmpe.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.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).