Please ask these stuff on the list. 1. You should use i686-w64-mingw32 for 32bit.
2. NSI build is not supported for cross compile, there openvpn developers prefer to use their own build system in order to produce the installer. 3. As openvpn is not modular, you must compile your self the tap driver and sign it, most people are not interested in that. A better alternative would have been to provide asigned .MSI for the tab driver and embed it into the openvpn .MSI. Alon. On Fri, Jul 1, 2011 at 11:56 PM, Bertrand Jacquin <be...@meleeweb.net> wrote: > > Hi, > > I'm tring to build openvpn from sources for Windows (x32 & x64) from > with gentoo toolchain (i686-pc-mingw32 x86_64-w64-mingw32) but I face to > some issue like how to sign drivers and why is there many nsi files like > : > > beber@otis /data/build/src/openvpn $ find . -name setpath.nsi | xargs sha1sum > c379b947d55e49ad7496d89c1e002986a367d572 ./gen/nsi/setpath.nsi > c379b947d55e49ad7496d89c1e002986a367d572 ./win/setpath.nsi > c379b947d55e49ad7496d89c1e002986a367d572 ./install-win32/setpath.nsi > beber@otis /data/build/src/openvpn $ find . -name openvpn.nsi | xargs sha1sum > 5c9c4d360c188017475e26d3a524d54deeee23b4 ./gen/nsi/openvpn.nsi > 1f00a55d49551487307c644214830a67ba55f6ea ./win/openvpn.nsi > 5c9c4d360c188017475e26d3a524d54deeee23b4 ./install-win32/openvpn.nsi > > Why do theses files are duplicated ? > > Thanks > > -- > Beber
