On 1/25/19 11:14 AM, Damjan Marion wrote:
> 
> 
>> On 25 Jan 2019, at 10:49, Marco Varlese <mvarl...@suse.de
>> <mailto:mvarl...@suse.de>> wrote:
>>
>> Hi Damjan,
>>
>> On 1/24/19 10:46 PM, Damjan Marion via Lists.Fd.Io wrote:
>>>
>>> In theory like any other cmake project:
>>>
>>> $ mkdir build
>>> $ cd build
>>> $ cmake /path/to/vpp/src <opt args>
>>> $ make
>>> $ make install
>> Hmmm, not sure if I explained myself in the right way.
>>
>> The problem today is that I cannot find a way to tell VPP _not_ to
>> download the dpdk tarball, uncompress it, build it and then link against
>> it...
> 
> That is exactly what I described above....
> 
>>
>> How does the above help in that regard?
> 
> It helps as cmake doesn't download dpdk or other libs. It is downloaded
> by bunch of makefiles outside of src/.
> If you don't need such service from those Makefiles, don''t use them..
OK, so I did try your suggestion but in that case the DPDK plugin
doesn't get built at all and the build procedure doesn't even get to the
point of looking for a DPDK library (whether statically or dynamically
linked).
> 
>>
>>>
>>> In practice probably few lines should be modified in
>>> src/plugins/dodkCMakeLists.txt to enable linking with shared libs, as
>>> today we do static...
>> So the shared-lib support was removed when moving to cmake I suppose.
>> Was that intentional or just a miss?
> 
> it was intentional miss :)
> 
> -- 
> Damjan
> 

-- 
Marco Varlese, Architect Developer Technologies, SUSE Labs
SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg        

Attachment: signature.asc
Description: OpenPGP digital signature

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12008): https://lists.fd.io/g/vpp-dev/message/12008
Mute This Topic: https://lists.fd.io/mt/29529767/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to