Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Valenzuela <jvalenzuela@dspfl.com>
To: buildroot@busybox.net
Subject: [Buildroot] User shared libraries
Date: Mon, 19 May 2008 14:19:37 -0400	[thread overview]
Message-ID: <4831C4B9.9080107@dspfl.com> (raw)

I've got a question regarding adding shared libraries to the buildroot 
system. This is my first time with the buildroot/uclibc/busybox system, 
so I forgive me if I miss something obvious.

I have the base root file system and toolchain compiled ok. I now wish 
to add a few of my own programs to run on the target system. Currently 
these programs of mine consist of a shared library and a binary that 
utilizes that shared library. By following the docs and looking at some 
of the other .mk files, I think I have the shared library installed ok. 
The .so files are in the correct target 
directory($(TARGET_DIR)/usr/lib). By using the --includedir option to 
the configure script, I *THINK* I got the headers to land in the right 
place also, build_ARCH/staging_dir/usr/include or more specifically 
$(STAGING_DIR)/usr/include.

Now comes that part I'm stuck on, the binary. Its configure script wants 
to see that the library is in fact installed, however it is not 
installed in the toolchain directory, only the headers are. It seems 
like I should install the shared library in both the target file system 
and in the toolchain. Is this correct? Any pointers to some 
docs/examples on how to do this?


Thanks,
Jason Valenzuela

                 reply	other threads:[~2008-05-19 18:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4831C4B9.9080107@dspfl.com \
    --to=jvalenzuela@dspfl.com \
    --cc=buildroot@busybox.net \
    /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