On Thu, May 10, 2012 at 3:23 PM, Samuli Seppänen <sam...@openvpn.net> wrote: > Il 10.05.2012 15:11, Samuli Seppänen ha scritto: >> Hi, >> >> I tried to generate a Windows installer on Ubuntu 11.10 amd64, but ran >> into some issues: >> >> $ cd openvpn-build/windows-nsis >> $ ./build-snapshot >> --- snip --- >> >> make[3]: Leaving directory >> `/home/samuli/opt/openvpn-build/windows-nsis/tmp/build-i686/pkcs11-helper-1.10' >> make[2]: Leaving directory >> `/home/samuli/opt/openvpn-build/windows-nsis/tmp/build-i686/pkcs11-helper-1.10' >> make[1]: Leaving directory >> `/home/samuli/opt/openvpn-build/windows-nsis/tmp/build-i686/pkcs11-helper-1.10' >> tap-windows >> Fixup libtool files >> Restore libtool files >> ls: cannot access tmp/image-i686/openvpn-i686-*-bin.*: No such file or >> directory >> >> The error message seems clear enough, but I'm wondering why the binaries >> are not where it looks for them: >> >> $ ls tmp/image-i686 >> openvpn >> $ ls tmp/image-i686/openvpn >> bin etc include lib share > > Oh, forgot to ask... is there a clean way to resume the build near the > failure point? Rebuilding everything every time is very time-consuming.
No.... sorry, I didn't think it worth the effort as dependencies build is one time and you can use regular openvpn configure && make against the dependencies while developing. But once you have the binary images you can use the windows-nsis/build script to only create installer out of them. Alon.
