“Make build” in the VPP directory will get you a debug build. The $1 and such 
is just standard shell scripting, in case I need to pass some parameters to 
vat. I don’t think I had ever needed them...

--a

> On 13 Nov 2017, at 17:40, Yuliang Li <yuliang...@yale.edu> wrote:
> 
> Maybe this is a stupid question.. Does vat have to work with debug builds? 
> And how to do the debug builds? What are the $1~$5 in your script?
> 
> Thanks,
> Yuliang
> 
>> On Mon, Nov 13, 2017 at 3:03 AM, Andrew Yourtchenko <ayour...@gmail.com> 
>> wrote:
>> When just running vat from within the source tree, it needs to know the path 
>> for the plugins, for debug builds I usually have the following small shell 
>> script which takes care of this without requiring me thinking every time (of 
>> course needs to be launched from the vpp top directory since it has relative 
>> paths:
>> 
>> $ cat ~/bin/run-vat
>> #!/bin/sh
>> sudo ./build-root/install-vpp_debug-native/vpp/bin/vpp_api_test plugin_path 
>> ./build-root/install-vpp_debug-native/vpp/lib64/vpp_api_test_plugins/ $1 $2 
>> $3 $4 $5
>> 
>> Not sure about the error with build-vat, I will let other folks comment on 
>> it if someone knows...
>> 
>> —a
>> 
>> > On 13 Nov 2017, at 03:14, Yuliang Li <yuliang...@yale.edu> wrote:
>> >
>> > Thanks for the quick reply.
>> >
>> > I still fail to use the vat to configure ACL. After make build-release, I 
>> > use sudo build-root/build-vpp-native/vpp/vpp_api_test, but it tell me:
>> > 'acl_plugin_get_version': function not found
>> > Other ACL commands have the same problem.
>> >
>> > I also tried make build-vat, but it gives the following error:
>> > @@@@ Arch for platform 'vpp' is native @@@@
>> > @@@@ Finding source for vpp-api-test @@@@
>> > @@@@ Package vpp-api-test not found with path /home/bright/tools/vpp @@@@
>> > Makefile:780: recipe for target 'vpp-api-test-find-source' failed
>> > make[1]: *** [vpp-api-test-find-source] Error 1
>> > make[1]: Leaving directory '/home/bright/tools/vpp/build-root'
>> > Makefile:460: recipe for target 'build-vat' failed
>> > make: *** [build-vat] Error 2
>> >
>> > Am I doing something wrong here?
>> >
>> > Thanks,
>> > Yuliang
>> >
>> > On Sun, Nov 12, 2017 at 5:15 PM, Andrew 👽 Yourtchenko <ayour...@gmail.com> 
>> > wrote:
>> > Hi Yuliang,
>> >
>> > You can look at the test/test_acl_plugin_*.py files for the examples
>> > of interactions with plugin from python code.
>> >
>> > Alternatively, you can use VPP API test tool (vat) which is built
>> > together with VPP and then issue the API calls directly from there.
>> >
>> > Shout if you have any questions, will be happy to answer! :)
>> >
>> > --a
>> >
>> > On 11/12/17, Yuliang Li <yuliang...@yale.edu> wrote:
>> > > Hi,
>> > >
>> > > I want to use the ACL plugin https://wiki.fd.io/view/VPP/SecurityGroups. 
>> > > It
>> > > seems it can only be configured via API. I only used vppctl before. Can
>> > > anyone please tell how to use the API to configure? Or is there other 
>> > > ways
>> > > to configre?
>> > >
>> > > Thanks,
>> > > --
>> > > Yuliang Li
>> > > PhD student
>> > > Department of Computer Science
>> > > Yale University
>> > >
>> >
>> >
>> >
>> > --
>> > Yuliang Li
>> > PhD student
>> > Department of Computer Science
>> > Yale University
>> 
> 
> 
> 
> -- 
> Yuliang Li
> PhD student
> Department of Computer Science
> Yale University
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Reply via email to