public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "McAllister, Colin" <Colin.McAllister@garmin.com>,
	Ulf Hermann <ulf.hermann@qt.io>
Cc: "elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>
Subject: Re: Building Elfutils with Mingw32
Date: Wed, 01 Nov 2023 14:15:47 +0100	[thread overview]
Message-ID: <527651f4ca70f7845e933013956427748a23d254.camel@klomp.org> (raw)
In-Reply-To: <SA2PR04MB77239C427ABF0F2F2D152ACBF4FBA@SA2PR04MB7723.namprd04.prod.outlook.com>

Hi,

On Mon, 2023-09-18 at 13:18 +0000, McAllister, Colin via Elfutils-devel
wrote:
> > There is a large number of developers who build software for ELF-based
> > embedded systems on windows and test/debug/profile/deploy it over some
> > network or USB connection. Those people want to have elfutils for their
> > debugging and profiling. They want to use elfutils on the host (the windows
> > box) because that is much faster.
> 
> This is also our use case. I support developers that use Windows on their host PC to develop Embedded Linux applications. I’m currently exploring options to provide Windows users the same development tooling to use GDB with Debuginfod for them to be able to debug Embedded Linux applications.
> 
> > Those people are not me and I'm not talking about sanity.
> 
> Likewise 😊
>  
> > > And why aren't people simply using cygwin for such a port?
> > 
> > If we built perfparser with cygwin, the people who use it would also need
> > cygwin. People building embedded devices generally have a colorful mess of
> > different tools, none of which you can rely on in advance. 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 would prefer to use MinGW instead of Cygwin.

So for those people preferring MinGW over Cygwin you still need some
posix/linux compatibility layer. It isn't clear to me what that needs
to be. It seems to become very complicated very quickly. For example
there is this patch series:

https://patchwork.sourceware.org/project/elfutils/list/?series=15310&state=*

I have reviewed and pushed various of those patches where they made
sense (to me). But as you can see there are various patches that were
just rejected and others where I really don't understand the real
issue/solution.

If someone could help reviewing those that would be really appreciated.

Thanks,

Mark

      parent reply	other threads:[~2023-11-01 13:15 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
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 [this message]

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=527651f4ca70f7845e933013956427748a23d254.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).