nt: Tuesday, November 11, 2014 3:17 PM
> > > To: Gonzalez Monroy, Sergio
> > > Cc: dev at dpdk.org
> > > Subject: Re: [dpdk-dev] building shared library
> > >
> > > Hi,
> > >
> > > after building DPDK libs as shared libraries and link
Hi,
after building DPDK libs as shared libraries and linking it, I'm back to my
first problem: rte_eal_driver_register() never gest called and my app
crashes since there are no drivers registered. As previously mentioned, in
regular DPDK user app this functions is called for every driver before
m
Hi Sergio,
no, that sounds good, thank you. Since I'm not that familiar with DPDK
build system, where should this option be set? In 'lib' folder's Makefile?
Thank you once again!
BR,
Newman
On Tue, Nov 11, 2014 at 3:18 PM, Sergio Gonzalez Monroy <
sergio.gonzalez.monroy at intel.com> wrote:
>
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Newman Poborsky
> Sent: Tuesday, November 11, 2014 3:17 PM
> To: Gonzalez Monroy, Sergio
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] building shared library
>
> Hi,
>
> afte
On Tue, Nov 11, 2014 at 01:10:29PM +0100, Newman Poborsky wrote:
> 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 appli
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_dri
> Cc: dev at dpdk.org
> > Subject: Re: [dpdk-dev] building shared library
> >
> > Hi,
> >
> > after building DPDK libs as shared libraries and linking it, I'm back to my
> > first problem: rte_eal_driver_register() never gest called and my app
&g
Hi Newman,
> From: dev [mailto:dev-bounces at 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) a
From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of ext Newman Poborsky
> Sent: Monday, November 10, 2014 10:23 PM
> To: dev at dpdk.org
> Subject: [dpdk-dev] building shared library
>
> Hi,
>
> is it possible to build a dpdk app as a shared library?
>
> I tried to put
n Poborsky
Sent: Monday, November 10, 2014 10:23 PM
To: dev at dpdk.org
Subject: [dpdk-dev] building shared library
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 .
On Mon, Nov 10, 2014 at 03:22:40PM +0100, Newman Poborsky wrote:
> is it possible to build a dpdk app as a shared library?
Yes it will work, with a bit of performance loss from the .so symbol lookup
overhead. You have to set some of the build config options to get it to work
though.
Matthew.
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.
After that i tried adding:
LDLIBS += -lrte_eal -lrte_mbuf -lrte_cmdline -lrte_timer
12 matches
Mail list logo