I’d rather not move the API test tool. It’s compiled into vpp itself these days, to facilitate binary API - and vpp_api_test - debugging.
I worked hard enough on the problem so that vpp manages to inhale vpp_api_test plugins, so that essentially the entire binary API can be exercised through the “binary-api” debug CLI... Maybe we ought to have a session on this general topic next Tuesday? Thanks… Dave From: [email protected] [mailto:[email protected]] On Behalf Of Jon Loeliger Sent: Friday, March 31, 2017 9:44 AM To: Jim Thompson <[email protected]> Cc: vpp-dev <[email protected]> Subject: Re: [vpp-dev] Out of Tree Build Failure on vnet/rewrite.h On Fri, Mar 31, 2017 at 7:34 AM, Jim Thompson <[email protected]<mailto:[email protected]>> wrote: Either that, or Cisco moves to builds apps the same way. You guys & gals break the tree for us about twice per month lately. Hi VPP-ites, That's maybe not such a bad notion. What about taking, say, the entire VAT piece out of VPP proper, and making it a standalone project that is built using an installed RPM/DEB VPP build instead? Sure, it would be a bit of a pain for some developer, but it would also help to crystalize the boundaries between VPP-proper and CLI/API users as well. As it is, there are some fairly serious cross-over issues that are discovered as we stumble through our development as an API-only-user application. (This issue, the CLI directly using some functions instead of an API, is what lead me to introduce a patch for the "set MAC address API", for example.) HTH, jdl
_______________________________________________ vpp-dev mailing list [email protected] https://lists.fd.io/mailman/listinfo/vpp-dev
