Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: xing.fan0302@googlemail.com (Xing Fan)
Subject: [ltt-dev] building ust for android/arm
Date: Wed, 20 Apr 2011 23:21:09 +0200	[thread overview]
Message-ID: <BANLkTimjCtBJtj8vvvtVT1iV9KYYhKp6=A@mail.gmail.com> (raw)
Message-ID: <20110420212109.Og6tT4jPUqIqAw4nLGYvy3LemkIKYi8lni8Zzhlt3Mk@z> (raw)
In-Reply-To: <e41c0729597f4f63270d84c12f3a96d7@mail.gmail.com>

Here are more description of my setting.
1. I placed the ust code in external/ folder.
2. my Android.mk file in external/ust-0.6 looks like this:
===========================================================
include $(call all-subdir-makefiles)

LOCAL_PATH := $(call my-dir)

include $(CLEAR_VARS)
LOCAL_MODULE := libust
LOCAL_SRC_FILES := libust-initializer.c
LOCAL_C_INCLUDES += \
        $(LOCAL_PATH) \
        $(LOCAL_PATH)/include \
        external/userspace-rcu-0.4.6
include $(BUILD_SHARED_LIBRARY)
===============================================================

 3. However, I have problems to build libust.so. The error msg is:  make:
*** No rule to make target `build/core/libust-initializer.c', needed by
`out/target/product/u8500/obj/SHARED_LIBRARIES/libust_intermediates/libust-initializer.o'.
Stop.

   It is very strange that the compiler tries to pick up
libust-initializer.c from build/core folder, even though I have specified
that the source file is in my LOCAL_PATH, which is external/ust-0.6;

 /Stella

On Wed, Apr 20, 2011 at 11:12 PM, Karim Yaghmour <karim.yaghmour at opersys.com
> wrote:

> Trimming content for brevity ...
>
> > -----Original Message-----
> > From: pdumas9@sympatico.ca [mailto:pdumas9@sympatico.ca] On Behalf Of
> Mathieu Desnoyers
> ...
> > * Xing Fan (xing.fan0302 at googlemail.com) wrote:
> ...
> > > I still think there is something wrong in my Android.mk file. If we
> read
> > > Makefile.am, it indicates to build a shared library called libust
> based on
> > > libust-initializer (I have treated this in my Android.mk). However, it
> seems
> > > Makefile does more than this. it builds/uses libust-initializer.o, I
> do not
> > > know how to put this in Android.mk file.
> > >
> > > Anyone has any hint?
> >
> > Sorry, I'm not familiar with the Android build infrastructure. Maybe
> > Karim might have some info here ? (see problem description below)
>
> I don't have enough information. Has libust been placed in aosp/external/.
> That's where it would usually go. Usually the best thing is to check how
> other packages in external/ are made to build part of the AOSP and do the
> same.
>
> As for the libust-initializer.c getting picked up, it looks like it's the
> EXTRA_DIST flag from Makefile.am creeping in. Again, I would need more
> info.
>
> --
> Karim Yaghmour
> CEO - Opersys inc. / www.opersys.com
> http://twitter.com/karimyaghmour
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/ltt-dev/attachments/20110420/94379bcd/attachment.htm>


  reply	other threads:[~2011-04-20 21:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20 17:37 Xing Fan
2011-04-20 17:37 ` Xing Fan
2011-04-20 17:37 ` Xing Fan
2011-04-20 18:12 ` Mathieu Desnoyers
2011-04-20 19:38   ` Xing Fan
2011-04-20 19:38     ` Xing Fan
2011-04-20 19:38     ` Xing Fan
2011-04-20 20:39     ` Mathieu Desnoyers
     [not found]     ` <BLU0-SMTP138D8FC21BF014372219BA96930@phx.gbl>
2011-04-20 21:12       ` Karim Yaghmour
2011-04-20 21:21         ` Xing Fan [this message]
2011-04-20 21:21           ` Xing Fan
2011-04-20 21:21           ` Xing Fan
2011-04-20 21:31           ` Mathieu Desnoyers
2011-04-20 23:20           ` Karim Yaghmour
2011-04-20 23:38 ` Matthew Khouzam
2011-04-20 23:38   ` Matthew Khouzam
2011-04-20 23:38   ` Matthew Khouzam

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='BANLkTimjCtBJtj8vvvtVT1iV9KYYhKp6=A@mail.gmail.com' \
    --to=xing.fan0302@googlemail.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