...and in fixing things, I am discovering that people have not been looking after their documentation. The index looks like a deranged lemming barfed up the last office party and called it production.
Chris. > -----Original Message----- > From: Damjan Marion (damarion) [mailto:damar...@cisco.com] > Sent: Wednesday, December 28, 2016 09:21 > To: Luke, Chris <chris_l...@cable.comcast.com> > Cc: vpp-dev <vpp-dev@lists.fd.io> > Subject: Re: change in source code tree > > > Same story, python bindings are moved, java bindings require care and > attention from > somebody fluent in java. Finally vpp-api/ should disappear. > > > > On 28 Dec 2016, at 15:18, Luke, Chris <chris_l...@comcast.com> wrote: > > > > Ditto /vpp-api and /src/vpp-api? > > > > The directories are referenced in the doc. > > > >> -----Original Message----- > >> From: Damjan Marion (damarion) [mailto:damar...@cisco.com] > >> Sent: Wednesday, December 28, 2016 08:51 > >> To: Luke, Chris <chris_l...@cable.comcast.com> > >> Cc: vpp-dev <vpp-dev@lists.fd.io> > >> Subject: Re: change in source code tree > >> > >> > >> Finally all plugins should go to src/plugins, but few of them have messy > >> japi generation inside makefiles, so that needs to be resolved first. > >> > >> thanks for fixing doxygen, such hiccups are expected with such a big > change. > >> > >> I’m fixing “make test” now which also have hardcoded paths… > >> > >> > >>> On 28 Dec 2016, at 14:46, Luke, Chris <chris_l...@comcast.com> wrote: > >>> > >>> I'm fixing up Doxygen for it; it passed verify because missing src > directories > >> was not fatal. > >>> > >>> What's the difference between "/plugins" and "/src/plugins"? > >>> > >>> Chris. > >>> > >>>> -----Original Message----- > >>>> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev- > boun...@lists.fd.io] > >> On > >>>> Behalf Of Damjan Marion (damarion) > >>>> Sent: Tuesday, December 27, 2016 20:35 > >>>> To: vpp-dev <vpp-dev@lists.fd.io> > >>>> Subject: [vpp-dev] change in source code tree > >>>> > >>>> Dear vpp-dev members, > >>>> > >>>> I just submitted a patch to gerrit[1] which introduces significant > >> improvement > >>>> in VPP build speed and also reduces complexity of the build system. > >>>> > >>>> Number of autotools instances is reduced to one, and whole code is > >> moved > >>>> under the src/ > >>>> tree. That effectively means that autoconf is called only once, and build > >> can > >>>> be > >>>> much more parallelized due to the flat structure of the Makefiles. > >>>> > >>>> Few plugins are migrated to the new tree, other will be moved later, > >> mainly > >>>> because > >>>> we need to improve whole japi build process first. > >>>> > >>>> New autoconf config is much more configurable, so different command > >> line > >>>> options > >>>> can be used to switch on/off specific components. Currently it looks > like: > >>>> > >>>> --enable-tests Enable unit tests > >>>> --enable-dpdk-shared Link dpdk with shared libs > >>>> --enable-perftool Enable perftool > >>>> --enable-g2 Enable g2 > >>>> --disable-vlib Disable vlib and dependant libs and binaries > >>>> --disable-svm Disable svm and dependant libs and binaries > >>>> --with-dpdk-crypto Use DPDK cryptodev > >>>> --with-dpdk Use DPDK > >>>> --without-ipsec Disable IPSec > >>>> --without-ipv6sr Disable IPv6 SR > >>>> --without-apicli Disable binary api CLI > >>>> --disable-sixrd-plugin Do not build sixrd plugin > >>>> --disable-ila-plugin Do not build ila plugin > >>>> --disable-flowperpkt-plugin > >>>> Do not build flowperpkt plugin > >>>> > >>>> > >>>> Now whole vpp can be build outside of git tree, i.e. > >>>> > >>>> mkdir ~/tmp/build > >>>> cd ~/tmp/build > >>>> ~/src/vpp/src/configure > >>>> make > >>>> > >>>> As this change is intrusive in the way that it moves all code to src/ > >>>> please let me know if there is any issue with merging this patch. > >>>> Based on the gerrit activity, looks like this is the right time to do it… > >>>> > >>>> Thanks and Happy Holidays! > >>>> > >>>> Damjan > >>>> > >>>> [1] https://gerrit.fd.io/r/#/c/4430/ > >>>> > >>>> _______________________________________________ > >>>> vpp-dev mailing list > >>>> vpp-dev@lists.fd.io > >>>> https://lists.fd.io/mailman/listinfo/vpp-dev > > _______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev