On Aug 11, 2014, at 4:01 PM, Ankur Sharma <ankursha...@vmware.com> wrote:
> Hi Ben, > > Thanks a lot for your reply. > > The reason we did not generate header file in build directory is because as > of now the windows datapath build is not coupled with user-space build. > The userspace build system is 'make' and command line based, and the kernel > is being compiled from Visual Studio. So, kernel code hardcodes the include > directory in precomp.h. > > One way to get around this issue is to pass a reference to the userspace > build directory while building the kernel. But, this is not straight forward > and would require messy hacks (given that we can build userspace and windows > driver on different machines as well.). > > That is the reason we decided to generate the file in src directory, which > can be included in kernel easily. In the long term, we should plan to move the Windows Datapath build infrastructure to command line based which would get invoked from the toplevel make similar to Linux. At that point, we can pass on the build directory path from the userspace build system to datapath's build system. Until then, we don't have much of an option than hardcoding header files that are part-of or build-generated from userspace. If there are cleaner ways of doing this, we can certainly incorporate that. thanks, Nithin _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
