[openbeos] Re: suggestions: iconv.h, libiconv, and iconv

  • From: "Andrew Bachmann" <shatty@xxxxxxxxxxxxx>
  • To: openbeos@xxxxxxxxxxxxx
  • Date: Thu, 31 Jul 2003 18:40:31 -0700 PDT

On Thu, 31 Jul 2003 15:37:35 +0200 CEST "Ingo Weinhold" 
<bonefish@xxxxxxxxxxxxxxx> wrote:
> On Wed, 30 Jul 2003 22:42:03 -0700 PDT "Andrew Bachmann" <
> shatty@xxxxxxxxxxxxx> wrote:
> [...]
> > 1. Build the so-called "plugin" version of gnu libiconv.so [this 
> > version publishes the API as 
> > iconv_open and not libiconv_open], and publish it as libiconv.so.  
> > This is possible by modifying a 
> > makefile slightly and manually requesting the plugin version.
> We can as well build the `normal' version and write the <iconv.h> 
> functions as simple wrappers for the GNU ones.

I'm okay with following this one too, especially since I got it working
"manually".  Should I check libiconv into our cvs somehow?  Perhaps
in current/src/libs/iconv?  The build system is configure/makefile, 
should I convert it to jam?

Also, are you proposing that we write iconv functions in the
header file that call libiconv functions?  I think it might be more
straightforward to just build it in plugin mode.

The only other nit I have left is how to address the prototype issue.

I can add the gnu iconv.h to headers/libs/iconv and build only
libiconv using it.  (gnu iconv.h has const and other messiness)
If the other apps use the public posix/iconv.h header
then the function will still presumably link. (right?)

As far as I can tell the posix standard is to not use const:


Other related posts: