On 08/14/2014 02:35 PM, Ola Liljedahl wrote:
ODP has a lot of dependencies (may be different for different ODP implementations). We cannot expect the ODP build system to be able to build all its dependencies as well. How this is done (e.g. install a prebuilt package, build from source etc) might be different for different platforms and use cases.
In fact we shouldn't be worrying about building dependencies. But the point is to provide a way to specify the location where the relevant header files are available (in case they are not in at standard location). To specify the parameter should be optional and if not specified they should be made available prior to building odp.
Where to look for specific (e.g. Netmap) header files and libraries is a different thing. Many ODP use cases involve cross compilation using a specific compiler and target system environment. How do we solve this in general in ODP? Doesn't Netmap fit into the current model of cross compilation?
Netmap is already a part of FreeBSD and we find the header files under sys/net/ directory. Just to satisfy the build I copied the header files from netmap directory to include directory within odp. Though the netmap version we have does not match the one considered by ODP and hence the build fails.
If we consider expanding the --enable-netmap configure script parameter to --enable-netmap=<netmap-src-dir> then all the Makefile needs to do is add "-I <netmap-src-dir>/sys/" to CFLAGS.
I've seen similar thing for supporting ODP on TI Keystone where --with-sdk-install-path is used to specify the directory where Keystone SDK would be available.
-- Regards, Tushar _______________________________________________ lng-odp mailing list [email protected] http://lists.linaro.org/mailman/listinfo/lng-odp
