Safest is to go with all combinations... Or at least: --disable-lzo --enable-lzo --enable-pkcs11 --disable-pkcs11 --enable-selinux --disable-selinux --enable-iproute2 --disable-iproute2 --disable-server --enable-small --disable-plugins --disable-management
--disable-crypto --disable-ssl --with-crypto-library=openssl --enable-crypo --enable-ssl --with-crypto-library=openssl --enable-crypo --disable-ssl --with-crypto-library=polarssl --enable-crypo --enable-ssl --with-crypto-library=polarssl --enable-crypo --disable-ssl And... for windows, you can use the build-complete script to produce a complete installer on Linux, if that's work you are good. Anyway... I want to question [again] these options... I think openvpn provides more flexibility than it should... there is no point to disable plugins nor management, cryptoless operation is also somewhat always required... It can make the code much simpler! 2012/3/30 Samuli Seppänen <sam...@openvpn.net>: > Hi all, > > Before Alon's buildsystem overhaul our buildbot farm tested building > with all unique combinations of the following build flags: > > --disable-lzo --disable-ssl, --disable-crypto, --disable-management > > In addition, each commit triggerer a build which used no build flags > (i.e. just ran "./configure"). > > What build flags should we test now? > > -- > Samuli Seppänen > Community Manager > OpenVPN Technologies, Inc > > irc freenode net: mattock > > > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ > Openvpn-devel mailing list > Openvpn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openvpn-devel
