public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: josh wojnas <josh_wolf@yahoo.com>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: Hi dev c++ uses the base debugger you mentioned & I would like to use that there was a sinple download.
Date: Thu, 06 Nov 2003 16:11:00 -0000	[thread overview]
Message-ID: <1068135264.1734.17.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <20031106052425.65274.qmail@web41205.mail.yahoo.com>

On Wed, 2003-11-05 at 21:24, josh wojnas wrote:
> Hi dev c++ uses the base debugger you mentioned & I would like to use
> that there was a sinple download. Where I install it over some
> directory and I am ready. Now I am useing windows so saying build ...
> is way out of my scope. I don't want to have to be a comp sci person
> to have to use your tool if it was acsessible by more people more
> would like it. etc. 

Never heard of "hi dev c++", but if you they say the use insight, then
let them supply binaries for it.

However, you also say that you're on windows. So that means the "hi dev
c++" is using gcc and gdb, which means that you will need Cygwin (a
posix layer for Windows). You will need to install cygwin anyway, and
cygwin *does* have binary insight packages available from the setup
application. Go to http://www.cygwin.com to install cygwin.

Of course, I admit that your following contradictory statements really
confuse me. You "don't want to have to be a comp sci person" and build
the tools, but you want to write applications in C/C++? 

[Building Insight, like almost any other free software application, is
actually quite easy, even on cygwin.]

Good luck.
Keith


      reply	other threads:[~2003-11-06 16:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-06  5:24 josh wojnas
2003-11-06 16:11 ` Keith Seitz [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=1068135264.1734.17.camel@lindt.uglyboxes.com \
    --to=keiths@redhat.com \
    --cc=insight@sources.redhat.com \
    --cc=josh_wolf@yahoo.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).