Hi Francesco, On 10/14/2015 10:02 AM, Francesco wrote: > Hi Olivier, > thanks for reviewing the patch. However for me it is logical that T= > option is used for "config" target and then for building/cleaning only > O= is used. However it is not logical for me that install target > requires T= option instead of O= option... or perhaps I'm missing something?
Actually, the current behavior of install target is to build one or several targets from templates given in the T=. To be clear, this line: make install T=*-native-linuxapp-gcc is equivalent to: make config T=i686-native-linuxapp-gcc O=i686-native-linuxapp-gcc make O=i686-native-linuxapp-gcc make config T=x86_64-native-linuxapp-gcc O=x86_64-native-linuxapp-gcc make O=x86_64-native-linuxapp-gcc make config T=x86_x32-native-linuxapp-gcc O=x86_x32-native-linuxapp-gcc make O=x86_x32-native-linuxapp-gcc The target name "install" is probably not well chosen, and that's probably why you are confused. Mario is currently reworking the Makefiles to support the installation of DPDK into a hierachical file system: http://dpdk.org/ml/archives/dev/2015-October/024686.html http://dpdk.org/ml/archives/dev/2015-October/025432.html Regards, Olivier
