> I'd say complain to Microsoft. If shared libs compiled with one version
> of the compiler are useless for programs that are compiled with the
> other, that's MS's problem, not ours. Well, theoretically, anyway...
Not that easy.
> > I'm not sure but I think apr-iconv looks in
> > the folder ./iconv (below the application folder)
> > if that env-variable is not set, at least there's
> > a #define in the source for that.
> > Would that be a solution to this problem?
>
> Not really, because you'd have to make sure that the working directory
> is the one where your program is installed. Alternatively, you could
> teach apr-iconv on Windows to use the dirname of the module filename as
> an alternative search path for the conversion modules, if APR_ICONV_PATH
> isn't defined.
I would do that the other way around: if the modules are present in the
application
subfolder then definitely use those ('cause the app installed and was
tested against those) and only if they're not there _then_ use the ones on
the
APR_ICONV_PATH.
> > Just not set the env-variable and force
> > the installer to copy those files to the
> > subfolder "iconv"?
> >
> > Suggestions?
>
>
> I would definitely like to see a solution that leta _all_ Subversion
> clients share the same apr-iconv conversion modules, preferably the ones
> installed with Apache (if you happen to have Apache installed). If that
> means downgrading to MSVC6 for all released binaries, then so be it.
Sorry, but that isn't possible. VS.NET came with many enhancements which
my client uses. So compiling isn't possible with VC6 - at least not with
major
changes in the sourcecode. And I don't like the idea of reinventing the
wheel
i.e. code myself what's already done in the libs which come with VS.NET.
Sure it would save some space on the harddisk if all clients would share
the same modules, but today's hd's are big enough. And I don't like the
idea that my client depends on modules which came with whatever other
program - no one can guarantee that those modules will work. So since
all clients must have those modules packed in the installer anyway (since
it's possible that _no_ other program installed those yet) I think it's
always
best to install them and use those.
And for a client you don't have to install the whole apache server.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 25 21:33:50 2003