Re: [Openvpn-devel] Windows Auto-Proxy

2011-08-08 Thread Heiko Hund
Hi, On Monday 08 August 2011 01:15:02 Russell Morris wrote: > Has anyone had any luck with the auto-proxy function, in particular with > PAC files? It really doesn't seem to be working for me ... :-(. Are you aware of https://community.openvpn.net/openvpn/ticket/24 ? This is probably what's caus

Re: [Openvpn-devel] Allow to fill Details tab for exe files

2011-08-08 Thread Heiko Hund
On Monday 08 August 2011 10:17:48 Bertrand Jacquin wrote: > > > Is there a windres equivalent for msvc ? > > There certainly a way to do the same thing using msvc or Python code > > that runs after the build. Does windres simply convert the resource file > > to another format? > > Yes and check th

Re: [Openvpn-devel] Allow to fill Details tab for exe files

2011-08-08 Thread Bertrand Jacquin
D'ar lun 08 a viz Eost 2011 e 10 eur 10, « Samuli Seppänen » he deus skrivet : > > > Looking to install-win32/makeopenvpn, it run autotools and configure, > > this may need some tweak : > > > > *inux) > > + export WINDRES=i586-mingw32msvc-windres I've updated my branch with a fix for that > > Is

Re: [Openvpn-devel] Allow to fill Details tab for exe files

2011-08-08 Thread Samuli Seppänen
> Looking to install-win32/makeopenvpn, it run autotools and configure, > this may need some tweak : > > *inux) > + export WINDRES=i586-mingw32msvc-windres > > Is there a windres equivalent for msvc ? There certainly a way to do the same thing using msvc or Python code that runs after the build. D

Re: [Openvpn-devel] Allow to fill Details tab for exe files

2011-08-08 Thread Samuli Seppänen
Il 08/08/2011 10:36, Samuli Seppänen ha scritto: - if I read this right, it will only work for the autoconf / mingw based build, but not for the msvc++ / python based build, right? will it co-exist, or break the python build? >>> I have to say that I didn't test with msvc++/p

Re: [Openvpn-devel] Allow to fill Details tab for exe files

2011-08-08 Thread Samuli Seppänen
>>> - if I read this right, it will only work for the autoconf / mingw based >>>build, but not for the msvc++ / python based build, right? will it >>>co-exist, or break the python build? >> I have to say that I didn't test with msvc++/python as I only use to >> cross compile applications