From: Ulf Hermann <ulf.hermann@qt.io>
To: "McAllister, Colin" <Colin.McAllister@garmin.com>,
elfutils-devel@sourceware.org
Subject: Re: Building Elfutils with Mingw32
Date: Thu, 14 Sep 2023 08:34:22 +0200 [thread overview]
Message-ID: <05996b4f-8464-ffdf-8629-c1e94aa73052@qt.io> (raw)
In-Reply-To: <SA2PR04MB7723A80F548491B3C0BF0BC1F4F0A@SA2PR04MB7723.namprd04.prod.outlook.com>
Hi,
keeping the windows/elfutils fork up to date definitely is a lot of
work, which is why I haven't found the time to do it for a while.
However, perfparser could in fact also use debuginfod (with some caveats).
I guess that some more of my patches could be upstreamed if properly
cleaned up. A rebase rather than a merge may be more conductive to this.
All I can do right now is tell you that I'd be happy about any
contribution. The repository I've been using still exists and accepts
outside contributions. See
https://codereview.qt-project.org/q/repo:qt-creator/elfutils . You have
to go through the Qt CLA process to work with it, but the CLA is largely
meaningless in this case. I'd be happy to move the repository to a more
"official" place without CLA.
There have also been other people on this mailing list talking about
porting elfutils to windows. Maybe if we combine our efforts we'll
actually find a way to maintain a port.
best regards,
Ulf
next prev parent reply other threads:[~2023-09-14 6:34 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 [this message]
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
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=05996b4f-8464-ffdf-8629-c1e94aa73052@qt.io \
--to=ulf.hermann@qt.io \
--cc=Colin.McAllister@garmin.com \
--cc=elfutils-devel@sourceware.org \
/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).