From: Mark Wielaard <mark@klomp.org>
To: Ulf Hermann <ulf.hermann@qt.io>,
"McAllister, Colin" <Colin.McAllister@garmin.com>
Cc: "elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>
Subject: Re: Building Elfutils with Mingw32
Date: Wed, 01 Nov 2023 14:05:48 +0100 [thread overview]
Message-ID: <da4980892087769beb80ff3bf4475ad3dc41d713.camel@klomp.org> (raw)
In-Reply-To: <8e392791-7bfd-7197-3ed8-5cfc1cbb21b3@qt.io>
On Sat, 2023-09-16 at 09:33 +0200, Ulf Hermann via Elfutils-devel
wrote:
> > I haven't considered shipping cygwin with perfparser. Is that actually
> > possible? It looks like it needs some installation procedure I would
> > have to burden the user with.
>
> I guess shipping cygwin with perfparser would make me a 3PP [1]. Sounds
> like fun.
>
> [1] https://www.cygwin.com/acronyms/#3PP
:) But I think the real solution would be for someone to package
elfutils for cygwin.
https://www.cygwin.com/packaging-contributors-guide.html
That way people that need the elfutils tools on windows can just get
them through cygwin. It might not be a total solution for people
needing to use the libraries when building for mingw with some other
posix compatibility layer, but it seems the best solution for just
getting the elfutils tools easily available on Windows.
It would be great if we could get some volunteer for packaging elfutils
for cygwin.
Cheers,
Mark
next prev parent reply other threads:[~2023-11-01 13:05 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
2023-09-16 7:17 ` Ulf Hermann
2023-09-16 7:33 ` Ulf Hermann
2023-11-01 13:05 ` Mark Wielaard [this message]
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=da4980892087769beb80ff3bf4475ad3dc41d713.camel@klomp.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).