From: Keith Seitz <keiths@cygnus.com>
To: Charles-Henri Balet <charles-henri@prolectronic.ch>
Cc: <insight@sources.redhat.com>
Subject: Re: compile CVS of insight
Date: Fri, 17 Aug 2001 13:38:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0108171331590.11484-100000@makita.cygnus.com> (raw)
In-Reply-To: <001301c1275b$63f3e500$0301a8c0@charlot>
On Fri, 17 Aug 2001, Charles-Henri Balet wrote:
> How compile the CVS of insight and dejagnu, I have download the CVS files
> like this :
>
> >CVS: Check out read-only copies from the GDB CVS repository with commands
> like these:
> >cvs -z9 -d :pserver:anoncvs@anoncvs.cygnus.com:/cvs/src login
> >{enter "anoncvs" as the password}
> >cvs -z9 -d :pserver:anoncvs@anoncvs.cygnus.com:/cvs/src co insight dejagnu.
> >Checking out and building both insight and dejagnu is recommended.
>
> and now I want to compile insight for arm-elf and user it under cygwin
>
> any can help me ?
Sure. It's (pretty simple).
I'll presume that you've already got Cygwin installed and working. If not,
you'll need to do that first. See http://www.cygwin.com . Insight on
windows is built on top of Cygwin.
Once you have your cygwin set up running and you can build simple
hello-world exeuctables, your ready to start building insight. Let's
assume that the sources you got from CVS are in "/home/chb/sources/src".
(It's the "src" directory that you got from cvs.) Then:
$ pwd
/home/chb/sources
$ mkdir cygwin-armelf
$ cd cygwin-armelf
$ ../src/configure --target=arm-elf \
--prefix=/home/chb/sources/built
[lots of stuff]
$ make all-gdb
[lots of stuff]
$ make install-gdb
When you get here, you will have your insight executable (arm-elf-gdb) in
/home/chb/sources/built/bin.
Take a look at gdb documentation for more information on building.
Insight is basically just a gui. Gdb is the debugger.
Good luck!
Keith
prev parent reply other threads:[~2001-08-17 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 13:28 Charles-Henri Balet
2001-08-17 13:38 ` 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=Pine.GSO.4.33.0108171331590.11484-100000@makita.cygnus.com \
--to=keiths@cygnus.com \
--cc=charles-henri@prolectronic.ch \
--cc=insight@sources.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).