public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Wendy Lin <wendlin1974@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Compile win64 filesys kernel module only with Cygwin tools?
Date: Thu, 10 Aug 2023 00:59:07 +0200	[thread overview]
Message-ID: <CA+j=ERoGxWuSBOXMpJ_mTdW9q=N+MGzERQT8wvBBfTp-aqVGYQ@mail.gmail.com> (raw)
In-Reply-To: <dce0b97a-e316-6645-bbf6-ea1f0973bc13@t-online.de>

On Wed, 9 Aug 2023 at 22:04, Hans-Bernhard Bröker via Cygwin
<cygwin@cygwin.com> wrote:
>
> Am 09.08.2023 um 21:17 schrieb Wendy Lin via Cygwin:
> > How can I compile
> > https://github.com/microsoft/Windows-driver-samples/tree/main/filesys/cdfs
> > with Cygwin gcc?
>
> You should not be trying to do that.
>
> That's deeply system-specific Windows code.  It has nothing to with
> POSIX, Cygwin or anything like that.

I really don't care. I really want to RUN AWAY (CRYING!!) from having
to depend on Visual Studio 2019 or later. I can't even find C:\WinDDK\
with Visual Studio 2019 anymore, after updating from Windows 8. I'm
almost crying about it.

Also, we want CI, and that is not going to happen with the Visual
Studio Community edition.

> For that you need a native Windows toolchain, and quite possibly some
> extra SDK packages from Microsoft to enable building them.  MinGW64
> (wether stand-alone, or the MSYS(2) hosted one, or the one hosted in
> Cygwin) might be able to do it.

So, MinGW64 would work? Which compiler and linker options do I have to
use, which libraries do I link against etc?

Wendy

  reply	other threads:[~2023-08-09 22:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 19:17 Wendy Lin
2023-08-09 20:03 ` Hans-Bernhard Bröker
2023-08-09 22:59   ` Wendy Lin [this message]
2023-08-10 19:50     ` Brian Inglis
2023-08-10 12:42   ` Martin Wege

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='CA+j=ERoGxWuSBOXMpJ_mTdW9q=N+MGzERQT8wvBBfTp-aqVGYQ@mail.gmail.com' \
    --to=wendlin1974@gmail.com \
    --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).