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

  • From: "Ingo Weinhold" <bonefish@xxxxxxxxxxxxxxx>
  • To: openbeos@xxxxxxxxxxxxx
  • Date: Fri, 01 Aug 2003 17:59:53 +0200 CEST

On Fri, 01 Aug 2003 11:42:33 +0200 CEST "Axel Dörfler" <axeld@pinc-
software.de> wrote:
> "Andrew Bachmann" <shatty@xxxxxxxxxxxxx> wrote:
> > On Thu, 31 Jul 2003 15:37:35 +0200 CEST "Ingo Weinhold" <
> > bonefish@xxxxxxxxxxxxxxx> wrote:
> > > 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?
> 
> Please not yet! As I said, we should have a deeper look at libroots 
> needs first, and decide where to put it when we did that.
> I don't think there is a point in putting it in now, only to have it 
> somewhere when it's going to be removed or moved soon (you remember, 
> stupid/simple CVS cannot move files around).

Does the location where it is checked in, in any way restrict, how it 
is used? I mean, we can still build a static library and link it into 
libroot. Or do you think of a tighter integration? That would make 
incorporating updates more complicated, I guess.

CU, Ingo


Other related posts: