From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Julian Brown <julian@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH/WIP] C/C++ wchar_t/Unicode printing support
Date: Fri, 30 Jan 2009 22:14:00 -0000 [thread overview]
Message-ID: <20090130194343.GA3964@adacore.com> (raw)
In-Reply-To: <m37i4dx64p.fsf@fleche.redhat.com>
Hi Tom,
I'm not very familiar with character encodings, so I won't review
the patch. However, something caught my attention:
> * With this patch, GDB requires iconv. I don't think it is a good use
> of our time to implement and maintain our own character set
> conversion library. I removed all the old code in charset.c that
> attempted this.
External dependencies of this sort can be a real issue. It's probably
not very hard as you mention to build it on our machines, but that
still leaves the problem of distribution. In other words, when we
distribute a GDB binary to one of our customers, we pretty much need
to distribute the iconv library as well.
Do you think we could have a configure option that allows us to
deactivate this feature in order to avoid the dependency? The other
alternative is to have a configure option that allows us to specify
where to look for the iconv library and headers. At our level, we
would then link GDB against the static libiconv. It makes the GDB
exe bigger but that's in exchange for an extra feature... In fact,
both options are actually independent and have merits on their own,
but either of them would be sufficient to help avoiding a dynamic
dependency on a shared library...
--
Joel
next prev parent reply other threads:[~2009-01-30 19:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 20:24 Julian Brown
2009-01-15 21:02 ` Tom Tromey
2009-01-15 21:18 ` Joseph S. Myers
2009-01-16 0:01 ` Tom Tromey
2009-01-15 22:16 ` Julian Brown
2009-01-16 0:53 ` Tom Tromey
2009-01-16 9:36 ` Eli Zaretskii
2009-01-16 16:18 ` Tom Tromey
2009-01-16 16:40 ` Eli Zaretskii
2009-01-16 16:57 ` Mark Kettenis
2009-01-30 4:11 ` Tom Tromey
2009-01-30 22:14 ` Joel Brobecker [this message]
[not found] ` <m3ocxos6og.fsf@fleche.redhat.com>
2009-02-01 18:23 ` Daniel Jacobowitz
2009-02-01 22:42 ` Tom Tromey
2009-02-01 23:16 ` Daniel Jacobowitz
2009-02-01 23:18 ` Daniel Jacobowitz
2009-02-01 23:26 ` Tom Tromey
2009-02-03 0:41 ` 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=20090130194343.GA3964@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=julian@codesourcery.com \
--cc=tromey@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