DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jose Gavine Cueto <pepedocs@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] dpdk shared lib build
Date: Sat, 02 Nov 2013 10:19:46 +0100	[thread overview]
Message-ID: <6749068.Cu70FoguaT@x220> (raw)
In-Reply-To: <CAJ5bv6HCngtoY+TcJCMT=jbHT9J0LK6sJzF_YpF=JYz9R+Mg8g@mail.gmail.com>

Hi,

02/11/2013 07:24, Jose Gavine Cueto :
> Building dpdk app. as a shared library (.so) I believe is supported but I
> can't find any documentation for it.  I tried doing the same Makefile
> format as building an app, and that is placed the following:
> 
> rte.vars.mk   ---------> before everything
> rte.extshared.mk -----------> after everything
> 
> At first make, spits the following error:
> 
>   INSTALL-SHARED
> cp: missing destination file operand after ‘/home/mydpdklib/src/build/lib’
> Try 'cp --help' for more information.
> make: *** [/home/linc/src/erlpmd.git/src/build/lib] Error 1
> 
> Second make, will do nothing, and lib does not contain any .so file.
>  Additionally I added  LIB = mylib.so

I think you should define SHARED variable instead of LIB.
Please confirm it works.

By the way, it is the old way of doing shared library. It should be deprecated 
and replaced by the new option RTE_BUILD_SHARED_LIB.

Could you also try the new method by using rte.extlib.mk with option 
CONFIG_RTE_BUILD_SHARED_LIB=y ?

Thank you
-- 
Thomas

      reply	other threads:[~2013-11-02  9:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 23:24 Jose Gavine Cueto
2013-11-02  9:19 ` Thomas Monjalon [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=6749068.Cu70FoguaT@x220 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=pepedocs@gmail.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).