All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Yates <yates@digitalsignallabs.com>
To: linux-bluetooth@vger.kernel.org
Subject: cross-compilation setup
Date: Tue, 05 Feb 2013 13:03:26 -0500	[thread overview]
Message-ID: <87vca6hc41.fsf@randy.site> (raw)

Hi,

I'm trying to ./configure, make, and make install bluez 5.2 into my
embedded linux project. I have a few questions on where things are
placed, which I would think are specified in the configure stage. Here
is my skeleton configure.mak with the specific questions.

So, apart from --sysconfdir, I don't see the options in README to
specify what I need. Can someone please help?

--Randy

# Author: Randy Yates
# Function: Bluez ./configure makefile
#
# this is my bluez configuration makefile. i wanted to have the
# configuration options recorded somewhere, and a makefile seemed to be
# a good choice. make -f configure.mak
#
# requires the following variables
# 
#   TARGET_ROOTFS
#   DEVELOPMENT_ROOTFS

# 1. what output does "make" generate? what executables, shared libraries, etc?
#
# 2. how do you specify the cross-compiler to use in make?
# 
# 3. what does "make install" install?
# 
#   a. the output in 1? to where? (needs to go into $(TARGET_ROOTFS)/usr/bin)
# 
#   b. the .h and other developer files? to where? (needs to go into $(DEVELOPMENT_ROOTFS)/inc, $(DEVELOPMENT_ROOTFS)/lib, etc. 
# 
#   c. documentation (manpages, etc.)? to where? (needs to go to /dev/null)
# 
#   d. what else and to where?
# 

-include Rules.make

.PHONY += configure
configure :
	./configure --prefix=/usr --sysconfdir=$(TARGET_ROOTFS)/rootfs-partial/etc --localstatedir=/var --disable-cups 


-- 
Randy Yates
Digital Signal Labs
http://www.digitalsignallabs.com

                 reply	other threads:[~2013-02-05 18:03 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=87vca6hc41.fsf@randy.site \
    --to=yates@digitalsignallabs.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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.