I think we can drop 32bit support once the 64bit is there. Thanks! Eitan -----Original Message----- From: Nithin Raju Sent: Monday, March 16, 2015 11:10 PM To: Alessandro Pilotti Cc: Eitan Eliahu; dev@openvswitch.org Subject: Re: [ovs-dev] OVS Windows MSI installer
> On Mar 15, 2015, at 7:54 PM, Alessandro Pilotti > <apilo...@cloudbasesolutions.com> wrote: > > > > >> On 16 mar. 2015, at 03:30, Eitan Eliahu <elia...@vmware.com> wrote: >> >> >> Alessandro, >> Yes, no problem of having the installer separate. But, I am confused as I >> see the two services are there but the driver and the INF file are not. I >> believe that the MSI file includes everything. >> Do you think you can add the OS installer script? >> Will we have already built MSI file (x86 and x86-64)? > > We'll commit the x64 MSI build code as soon as we have the x64 OVS build > merged upstream. > > One thing that we should decide is if it makes sense to keep a separate x86 > build at all at that point. > > Since Hyper-V is limited to x64, the only use case for a x86 build is for a > 32bit client OS build where a user wants to install the CLI tools only. > Given how limited this use case is, I'd go with a single x64 build. This is fine. If the x64 binaries can be built reliably and pass the tests, I think we can flip the switch on the default “mode” and just go with x64 binaries. I maybe wrong, but there’s no real usecase for 32 bit binaries on Hyper-V. -- Nithin _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
