From: Dave Murphy <davem@devkitpro.org>
To: insight@sourceware.org
Cc: keiths@redhat.com
Subject: Re: Insight CVS and MingW
Date: Sat, 08 Jan 2011 22:33:00 -0000 [thread overview]
Message-ID: <AANLkTik5g4S=Q0LdGTf0dskLw5CGAeELjyaYkZPW1Qw6@mail.gmail.com> (raw)
In-Reply-To: <4D0912A0.4070302@redhat.com>
On Wed, Dec 15, 2010 at 7:10 PM, Keith Seitz <keiths@redhat.com> wrote:
>
> On 12/12/2010 12:11 PM, Michael Trensch wrote:
>
>> I am currently trying to build a MingW Version of Insight to be able to
>> debug a ARM evaluation board using openOCD as gdbserver. I was tired of
>> using cygwin as I got into trouble when multiple applications were using
>> different cygwin dll's.
>
> Thank you for your support. For several weeks now, I've had MinGW working (or at least as much as I've tried). I will dig up my patches later today and post them to this list.
>
> So far, your patches look similar to mine. I guess that means I'm not entirely in "left field." :-)
>
> Keith
Any word on your patches Keith? I've just had a go with CVS using
Michael's patches and it all looks good for a powerpc-eabi target so
far.
Is it possible to build Insight with multiple targets enabled? I'm
about to have a go at arm-eabi but I just wondered if I could enable
both in a single binary or would it be better to just build them
separately? So far I've been building multiple binaries installed in
the same path for arm-eabi, powerpc-eabi and a slightly customised
mips target so they all share the tcl/tk parts. If it's easier to work
with multiple binaries is there some way to configure so I don't have
to build and install the tcl/tk libs multiple times?
Dave
PS: Sorry if you got this twice Keith, I messed up and managed to send
an html message to the list that got bounced.
next prev parent reply other threads:[~2011-01-08 22:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 20:11 Michael Trensch
2010-12-15 19:10 ` Keith Seitz
2011-01-08 22:33 ` Dave Murphy [this message]
2011-01-10 21:53 ` Keith Seitz
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='AANLkTik5g4S=Q0LdGTf0dskLw5CGAeELjyaYkZPW1Qw6@mail.gmail.com' \
--to=davem@devkitpro.org \
--cc=insight@sourceware.org \
--cc=keiths@redhat.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).