Works like a charm.
I probably should have specified in my ebuild remarks that I was simply
very happy that building the big piece of the pie under src with only
autotools, as shown in your note, and hence no ebuild involvement for that
part of the pie is now supported.
Burt
On Wed, Dec 28, 2016
Dear Burt,
> On 28 Dec 2016, at 15:08, Burt Silverman wrote:
>
> Hi Damjan,
>
> This looks really sweet. Finally, good riddance to ebuild.
This change is not about getting a rid of ebuild, ebuild is still there.
Main goal here was to reduce number of packages and speed up build process.
Autot
Hi vpp dev team,
In a very simple case if vpp is running on a single core then it's utilize 100%
due to its busy loop nature.
Is any way in VPP to limit the core/CPU usage? We would like for example to
configure VPP to use only a half of the specific core.
Or like in Linux NAPI to see that if no
...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.co
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 wrote:
>
> Ditto /vpp-api and /src/vpp-api?
>
> The directories are referenced in the doc.
>
>> -Origi
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
> Cc: vpp-dev
> Subject: Re: change in source code tree
>
>
> Fina
Hi Damjan,
This looks really sweet. Finally, good riddance to ebuild. Ebuild has a mix
of some brilliant tricks and some useless irritations. The brilliant tricks
were primarily designed for the case of building a slew of open source
packages, rather than something like VPP that wishes to be a sin
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 20
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 (d
Hi, all, thanks for your time.
Please help me to check this, how to fix this compile error, thanks.
It's ok on some vms, but not all vms, why.
Building vlib in /usr/src/vpp1609/build-root/build-vpp-native/vlib
make[2]: Entering directory `/usr/src/vpp1609/build-root/build-vpp-native/vl
10 matches
Mail list logo
