"Gary V. Vaughan" wrote:
> > Any argument why that is how it is?
>
> See my last mail.
>
> I can think of two ways around this. Either
> [[...]] or libtool would need to build a wrapper program on Windows
> which would call the wrapper script to set the environment up to load the
> correct DLLs and then call the actual program in the .libs subdirectory.
>
> The first option seems to be the easiest, and I believe Edward's patch
> addresses this problem.
Yummy. I think you could also write a single program that, when
run as mumble.exe interprets mumble.cfg. I think that would likely
be found easier than spinning a special purpose mumble.c / mumble.exe.
