Right but that's for running the unit tests right? I'm not running unit tests, I'm actually just using the python API in another application that controls/monitors VPP.
Thanks, Chris. > On Mar 27, 2020, at 6:45 PM, Paul Vinciguerra <pvi...@vinciconsulting.com> > wrote: > > From the test/Makefile: > $(PYTHON_INTERP) -m pip install -e $(PAPI_PYTHON_SRC_DIR)" > > On Fri, Mar 27, 2020 at 6:42 PM Christian Hopps <cho...@chopps.org> wrote: > Hmm, at least on 19.08 doing the papi-wipe/wipe-papi is only removing things > under test. I'm running an external python app (not under test) and it's > looking in the install directory which isn't updated after the wipe-papi. > > I found a hack/workaround which is to touch the CMakeLists.txt file in > src/vpp-api/python, though. That CMakeLists.txt just has an install command > so I guess it's not setting up any dependencies? > > Thanks, > Chris. > > > On Mar 27, 2020, at 6:30 PM, Paul Vinciguerra <pvi...@vinciconsulting.com> > > wrote: > > > > try 'test-wipe-papi'. > > You may need: > > > > https://gerrit.fd.io/r/c/vpp/+/26177 > > > > On Fri, Mar 27, 2020 at 6:26 PM Christian Hopps <cho...@chopps.org> wrote: > > [on 19.08] > > > > I'm seeing something odd building. When I "make build" after changing > > something in "src/vpp-api/python/vpp_papi/*.py" it does not get reinstalled > > in the build-root. In fact if I delete > > build-root/install-vpp_debug-native/lib64/python3.6/site-packages/vpp_papi* > > it also does not get reinstalled with a "make build". > > > > I guess vpp_papi is not fully integrated into the cmake build system? Short > > of fixing that, is there a way to force it to reinstall? > > > > Thanks, > > Chris. > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15914): https://lists.fd.io/g/vpp-dev/message/15914 Mute This Topic: https://lists.fd.io/mt/72599377/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
