Hi Alon, > Safest is to go with all combinations... Testing all combinations would be best, but there are a _lot_ of them... then you need to multiply that with the number of buildslaves (atm ~10) :). > 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 Sounds good to me. Any additions / opinions from somebody else?
> And... for windows, you can use the build-complete script to produce a > complete installer on Linux, if that's work you are good. Buildbot 0.8.5 (current version) supports Windows buildslaves, so that's on my TODO... might take a while, though. With cross-compiling on *NIX for Windows working properly, I could perhaps repurpose the Windows build computer as a buildslave. Samuli
