public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "McAllister, Colin" <Colin.McAllister@garmin.com>
Cc: Ulf Hermann <ulf.hermann@qt.io>,
	"elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>
Subject: Re: Building Elfutils with Mingw32
Date: Fri, 15 Sep 2023 23:00:56 +0200	[thread overview]
Message-ID: <20230915210056.GA5558@gnu.wildebeest.org> (raw)
In-Reply-To: <SA2PR04MB7723D417EE6FB634173B9CC3F4F7A@SA2PR04MB7723.namprd04.prod.outlook.com>

Hi Colin, Hi Ulf,

On Thu, Sep 14, 2023 at 07:44:08PM +0000, McAllister, Colin via Elfutils-devel wrote:
> I did see that there were quite a few patches sent to the ML toward the end of 2022 that attempted to add Windows support.
> https://sourceware.org/pipermail/elfutils-devel/2022q4/005449.html
> https://sourceware.org/pipermail/elfutils-devel/2022q4/005667.html
> 
> It looks like some of the patches were merged, but quite a few were never applied. I'm wondering if it'd be possible to finish adding support upstream such that a fork would no longer be needed?
> 
> I would be happy to help contribute however I can.

Thanks. It would be nice if elfutils was a bit more portable.  The
trouble is that not many people have that much experience with
Windows.  At least I have none.  When reviewing these patches I always
get really confused. And I don't fully understand the use case. Given
that Windows doesn't even use ELF why would you even want elfutils on
such a platform? And why aren't people simply using cygwin for such a
port. Without it you don't even have a normal POSIX like system. And
when using mingw do people still use a normal gcc compiler (to cross
build)? Or is the goal to build with some alternative windows
compiler?

But all that really is my confusion. It does make reviewing these
change proposals really hard though. Because I often don't know
whether some abstraction is really needed. And I do worry about
unnecessary abstractions/ifdefs/code because it is unclear how to
maintain them long term if I am not sure why.

But if there is consensus (among the Windows hackers) about using one
common target for the port then maybe we should have an official
branch on sourceware?

Also there is a mingw container setup on builder.sourceware.org which
we might use for doing CI on the port?
https://sourceware.org/cgit/builder/tree/builder/containers/Containerfile-fedora-mingw

Thanks,

Mark

  parent reply	other threads:[~2023-09-15 21:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13 21:08 McAllister, Colin
2023-09-13 21:34 ` Frank Ch. Eigler
2023-09-14  6:34 ` Ulf Hermann
2023-09-14 19:44   ` McAllister, Colin
2023-09-15  6:57     ` Ulf Hermann
2023-09-15 15:42       ` McAllister, Colin
2023-09-15 21:00     ` Mark Wielaard [this message]
2023-09-16  7:17       ` Ulf Hermann
2023-09-16  7:33         ` Ulf Hermann
2023-11-01 13:05           ` Mark Wielaard
2023-09-16 19:24         ` Milian Wolff
2023-09-18 13:18         ` McAllister, Colin
2023-09-18 15:45           ` Frank Ch. Eigler
2023-11-01 13:15           ` Mark Wielaard

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=20230915210056.GA5558@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=Colin.McAllister@garmin.com \
    --cc=elfutils-devel@sourceware.org \
    --cc=ulf.hermann@qt.io \
    /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).