Hello, all I am trying to determine how to best incorporate the latest OpenVswitch datapath module into an in-kernel build. Our situation is that we do (Canadian) cross-builds on x86 hardware for various ARM-based architectures which will have OpenEmbedded filesystems as their run-time environment. The target platforms lack both the RAM and the build-time dependencies needed to perform native (eg. dkms) module builds.
It appears that your development tree is optimized for more typical distros where dkms or module assistant may be used to rebuild the datapath module in the native environment each time the kernel is upgraded. Since our runtime environment does not permit this, I am searching for a solution which will allow autotools to properly configure your build tree and generate an openvswitch.ko datapath module from within a cross-development environment - preferably at the same time we are cross-building the kernel. I am writing in the hope that someone among the project developers can save me some research time and point me to the cleanest approach. Are there hooks within your build scripts to facilitate building the latest datapath module from within a kernel build? If so, can you provide some instruction as to how to employ them? Regrettably I am not expert enough in the detailed workings of autoconf and automake to immediately recognize the correct build-time variable settings to accomplish this based just upon a cursory examination of the various scripts included in your tree. Any pointers or help you may offer would be appreciated. Gary S. Robertson Linaro
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
