Re: [dpdk-dev] [PATCH] mk: fix printing target name when build completes

On Tue, Jul 30, 2019 at 11:35:52PM +0200, Thomas Monjalon wrote: > 04/06/2019 11:21, kka...@marvell.com: > > --- a/config/defconfig_x86_64-native-linuxapp-gcc > > +++ b/config/defconfig_x86_64-native-linuxapp-gcc > > +CONFIG_RTE_EXEC_ENV="linux" > > Why do you do this change in this file? > > I t

Re: [dpdk-dev] [PATCH] mk: fix printing target name when build completes

04/06/2019 11:21, kka...@marvell.com: > --- a/config/defconfig_x86_64-native-linuxapp-gcc > +++ b/config/defconfig_x86_64-native-linuxapp-gcc > +CONFIG_RTE_EXEC_ENV="linux" Why do you do this change in this file? I think changing this variable can break backward compatibility.

[dpdk-dev] [PATCH] mk: fix printing target name when build completes

From: Krzysztof Kanas The configuration for native-linux-* targets is done using symbolic links, e.g config/defconfig_x86_64-native-linux-gcc which points to config/defconfig_x86_64-native-linuxapp-gcc. When configuring mk will output correct target based on RTE_CONFIG_TEMPLATE. When building m