>Hi, > >2016-02-09 11:35, Keith Wiles: >> Adding support to the build system to allow for Makefile.XXX >> extention to a subtree, which already has Makefiles. These >> Makefiles could be from the autotools and others places. Using >> the Makefile extention RTE_MKFILE_SUFFIX in a makefile subtree >> using 'export RTE_MKFILE_SUFFIX=.XXX' to use Makefile.XXX in >> that subtree. >> >> The main reason I needed this feature was to integrate a autotool >> open source projects with DPDK and keep the original Makefiles. > >Sorry I fail to understand why it is needed. >Are you trying to add autotool in DPDK? I don't think it is a good approach. >The DPDK must provide a pkgconfig interface to be integrated anywhere.
I was not trying to add autotools to DPDK. On a number of times I wanted to integrate a open source project(s) with DPDK and use DPDK?s build system, but because the open source project already contained Makefile files you can not use DPDK build system without modify or moving the original Makefile files. Using this method I can just add a exported variable and supply my own Makefile.XXX files. One case was building FreeBSD source, but I did not want to modify FreeBSD Makefiles (or reply on previous built Makefiles as they would not work on Linux anyway) as I was pulling the source down from freebsd.org repo. Using a patch to add the Makefiles with a different suffix allows me to build FreeBSD using DPDK, without having to modify or own the FreeBSD source. I have had this problem a number of times with open source code I did not want to modify, but just build within DPDK build system and adding the support for a different suffix to DPDK provided a clean way. The change does not effect the correct build system and just allows someone to define a new suffix for a given subtree in the code. > Regards, Keith
