From: Wido den Hollander <wido@42on.com>
To: Rafael Shuker <k.z.shuker@gmail.com>, ceph-devel@vger.kernel.org
Subject: Re: Linking libraries into librados
Date: Mon, 16 Feb 2015 14:08:54 +0100 [thread overview]
Message-ID: <54E1EBE6.1010500@42on.com> (raw)
In-Reply-To: <CAApbOGp44pvpTUZd2FMxiJJjLG_ckKLQ+Xyqpo2nudc8x3Qb3g@mail.gmail.com>
On 15-02-15 06:15, Rafael Shuker wrote:
> Hey guys,
>
> This is my first time posting to this list, and I am a newbie in Ceph
> development.
>
> I am trying to write new functions into librados.cc and call external
> libraries from that very function.
>
> My problem is that I can't get my head around this build system when
> using ./run-make-check.sh and adding a new <some-library-path>.a to
> the src/librados/Makefile.am is giving me a headache.
>
> I have successfully adjusted librados.cc and librados.h to do some
> what I wanted, but whenever I reference a function in my external
> library I get a undefined reference exception during compilation. I
> have assumed that this is because I am not linking the library
> correctly and would like to know what the correct way to link a .a
> library for librados.cc.
>
> TLDR: What is the correct way to add a library for librados.cc?
>
To understand this correctly. You are not using librados, but you are
trying to modify librados by adding a external library in there?
> Thank you all for your help, please tell me if I can provide any more
> information.
>
> Cheers
>
> Rafa.
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Wido den Hollander
42on B.V.
Phone: +31 (0)20 700 9902
Skype: contact42on
prev parent reply other threads:[~2015-02-16 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 5:15 Linking libraries into librados Rafael Shuker
2015-02-16 13:08 ` Wido den Hollander [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=54E1EBE6.1010500@42on.com \
--to=wido@42on.com \
--cc=ceph-devel@vger.kernel.org \
--cc=k.z.shuker@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.