From: Hannes Domani <ssbssa@yahoo.de>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: building gdb with TUI support on Windows
Date: Sun, 28 Dec 2014 17:09:00 -0000 [thread overview]
Message-ID: <1750170338.2037036.1419786533157.JavaMail.yahoo@jws11163.mail.ir2.yahoo.com> (raw)
In-Reply-To: <CAHOBVAeGjDO4Vq8KqL-Xt6HoaTqbP+70zZ1gav-qVTO7amsLkg@mail.gmail.com>
> Ofir Cohen <ofircohenn@gmail.com> schrieb am 17:41 Sonntag, 28.Dezember 2014:
> Hi Hannes,
> Thanks a lot for the reply.
>
> It seems like one has to hack his own way through the code,
> and concrete steps / further description will be very helpful in my case.
>
> > I only had to change tputs() a bit.
> Could you please describe what changes are required there?
> I just commented it out, but I'm not sure that's enough.
I just changed it so that it actually does something:
--- a/pdcurses/terminfo.c
+++ b/pdcurses/terminfo.c
@@ -211,5 +211,8 @@ int tputs(const char *str, int affcnt, int (*putfunc)(int))
{
PDC_LOG(("tputs() - called\n"));
- return ERR;
+ while (*str)
+ putfunc(*str++);
+
+ return 0;
}
> > Since then I switched to pdcurses, it works much better (+faster) on windows.
> What environment and configuration did you use for building it?
> Do you just:
> ./configure --prefix=/mingw
> make
> make install
>
> and build gdb (in my case it's msys/msys2)?
>
> Or you needed to hack a little bit more (since PDCurses will not be
> found by default by configure)
> by adding for example some symbolic links from pdcurses libraries to ncurses?
I used the win32/gccwin32.mak:
make -f win32/gccwin32.mak pdcurses.a
After renaming pdcurses.a to libcurses.a, I moved curses.h/term.h/libcurses.a where gdb-configure needed it.
I think that's all.
next prev parent reply other threads:[~2014-12-28 17:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 0:13 Ofir Cohen
2014-12-26 8:04 ` Eli Zaretskii
2014-12-27 13:53 ` Ofir Cohen
[not found] ` <CAHOBVAdux2M9aRnkJh1hDm_9VCTD6kVzWkF2fjj84qy8UJuh7w@mail.gmail.com>
2014-12-27 14:13 ` Eli Zaretskii
2014-12-27 14:40 ` Hannes Domani
2014-12-27 18:32 ` Eli Zaretskii
2014-12-28 13:58 ` Hannes Domani
2014-12-28 16:41 ` Ofir Cohen
2014-12-28 17:09 ` Hannes Domani [this message]
2014-12-28 23:34 ` Ofir Cohen
2014-12-29 0:41 ` Hannes Domani
2014-12-29 15:28 ` Ofir Cohen
[not found] ` <946370725.2390231.1419869855237.JavaMail.yahoo@jws11110.mail.ir2.yahoo.com>
2014-12-29 16:20 ` Hannes Domani
2014-12-30 19:15 ` Hannes Domani
2014-12-30 20:10 ` Ofir Cohen
2014-12-30 20:39 ` Hannes Domani
2014-12-31 16:34 ` Eli Zaretskii
2015-01-01 12:28 ` Hannes Domani
2015-01-01 15:42 ` Eli Zaretskii
2014-12-31 21:12 ` Ofir Cohen
2015-01-01 14:26 ` Hannes Domani
2015-01-01 15:14 ` Ofir Cohen
2015-01-01 15:47 ` Eli Zaretskii
2015-01-01 16:33 ` Ofir Cohen
2015-01-01 16:42 ` Eli Zaretskii
2015-01-01 16:48 ` Joel Sherrill
2015-01-01 17:18 ` Eli Zaretskii
[not found] ` <CAHOBVAcF824319G6O_LfJBYAQP3M0-LbhAV_d=SrR6jM4=0k5w@mail.gmail.com>
[not found] ` <83d26ybcap.fsf@gnu.org>
2015-01-02 0:32 ` Ofir Cohen
2014-12-28 18:38 ` Sergio Durigan Junior
2014-12-29 2:43 ` Joel Brobecker
2014-12-29 3:15 ` Joel Sherrill
2014-12-29 3:21 ` Joel Brobecker
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=1750170338.2037036.1419786533157.JavaMail.yahoo@jws11163.mail.ir2.yahoo.com \
--to=ssbssa@yahoo.de \
--cc=gdb@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