DPDK patches and discussions
 help / color / mirror / Atom feed
From: Newman Poborsky <newman555p@gmail.com>
To: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] building shared library
Date: Tue, 11 Nov 2014 13:10:29 +0100	[thread overview]
Message-ID: <CAHW=9Pt0R_Zu7a9Bbue+eFRhyLoQ12uup27juWFB+HfpWeuKCQ@mail.gmail.com> (raw)
In-Reply-To: <91383E96CE459D47BCE92EFBF5CE73B004E9D503@IRSMSX108.ger.corp.intel.com>

Hi,

I want to build one .so file with my app (it contains API that I want to
call through JNI) and all DPDK libs that I use in my app.

As I've already mentioned, when I build and start my dpdk app as a
standalone application, I can see that before main() is called, there is a
call to 'rte_eal_driver_register()' function for every driver. When I build
.so file, this does not happen and no driver is registered so everyting
after rte_eal_init() fails.


BR,
Newman

On Tue, Nov 11, 2014 at 11:37 AM, Gonzalez Monroy, Sergio <
sergio.gonzalez.monroy@intel.com> wrote:

> Hi  Newman,
>
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Newman Poborsky
> > Sent: Monday, November 10, 2014 2:23 PM
> >
> > Hi,
> >
> > is it possible to build a  dpdk app as a shared library?
> >
> > I tried to put 'include $(RTE_SDK)/mk/rte.extshared.mk' in my Makefile
> (and
> > define SHARED) and it builds .so lib, but all rte_* symbols are
> undefined.
> >
> Can you elaborate a bit on how you are building DPDK and your app?
> Is your objective to build a single .so containing your app and all DPDK
> libs?
> Or do you want your app to have a link dependency on DPDK shared libs?
>
>

  reply	other threads:[~2014-11-11 12:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10 14:22 Newman Poborsky
2014-11-11  1:01 ` Matthew Hall
2014-11-11  3:28 ` Chi, Xiaobo (NSN - CN/Hangzhou)
2014-11-11  7:29   ` Newman Poborsky
2014-11-11 10:37 ` Gonzalez Monroy, Sergio
2014-11-11 12:10   ` Newman Poborsky [this message]
2014-11-11 14:18     ` Sergio Gonzalez Monroy
2014-11-11 14:44       ` Newman Poborsky
2014-11-11 15:16         ` Newman Poborsky
2014-11-11 15:26           ` De Lara Guarch, Pablo
2014-11-11 15:54             ` Neil Horman
2014-11-11 16:24               ` Newman Poborsky

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='CAHW=9Pt0R_Zu7a9Bbue+eFRhyLoQ12uup27juWFB+HfpWeuKCQ@mail.gmail.com' \
    --to=newman555p@gmail.com \
    --cc=dev@dpdk.org \
    --cc=sergio.gonzalez.monroy@intel.com \
    /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).