From: "Arevalo, Mario Alfredo C" <mario.alfredo.c.arevalo@intel.com>
To: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Question about combine libs option
Date: Fri, 19 Feb 2016 15:30:27 +0000 [thread overview]
Message-ID: <6594B51DBE477C48AAE23675314E6C460F7FE49A@fmsmsx107.amr.corp.intel.com> (raw)
In-Reply-To: <56C6F2F3.6070100@intel.com>
Thank you so much for your help Sergio
Regards,
Mario.
________________________________________
From: Gonzalez Monroy, Sergio
Sent: Friday, February 19, 2016 2:48 AM
To: Arevalo, Mario Alfredo C
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Question about combine libs option
On 18/02/2016 20:10, Arevalo, Mario Alfredo C wrote:
> Hi, good day, I have a question related to CONFIG_RTE_BUILD_COMBINE_LIBS option in DPDK configuration file,
> It's not clear for me what is the behavior of this option but it seems that when I enabled this option
> all libraries were combined to one single library called libdpdk.so (I enabled CONFIG_RTE_BUILD_SHARED_LIB too),
> is this correct?
That is correct.
Now, you can use COMBINE_LIB with or without SHARED_LIB.
The result is, as you said, combining all DPDK libraries into a single
library.
> or which other effects can produce this option, and if someone has a document about this
> option would be amazing :), thank you so much for your attention.
I don't think there is any info/doc regarding those config options
(someone else can correct me on this),
but I would think that the GSG (Getting Started Guide) would be a good
place to add such doc.
Sergio
> Regards.
> Mario.
prev parent reply other threads:[~2016-02-19 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 20:10 Arevalo, Mario Alfredo C
2016-02-19 10:48 ` Sergio Gonzalez Monroy
2016-02-19 15:30 ` Arevalo, Mario Alfredo C [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6594B51DBE477C48AAE23675314E6C460F7FE49A@fmsmsx107.amr.corp.intel.com \
--to=mario.alfredo.c.arevalo@intel.com \
--cc=sergio.gonzalez.monroy@intel.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).