Thanks. I didn't realize that replying would not automatically send it
to the group.
On Wed, Aug 18, 2010 at 9:42 PM, Frank Maker <[email protected]> wrote:

> Please respond to the Google Groups thread so others can learn from
> our discussion.
>
> 1) Yes, you can change LOCAL_MODULE to whatever you want the output
> from the Makefile to be called.
>
> 2) Assuming whatever is looking for libsensors.so is dynamically
> linked, then you should be able to just drop it in at runtime and the
> program will pick it up. If this does not seem to happen, use "ldd" to
> ensure that the object/executable is actually looking for this
> library.
>
> Good luck,
>
> Frank
>
>
> On 08/16/2010 08:14 AM, John Koshi wrote:
> > Hi Frank,
> >
> > Sorry, my question should have been: Can I change the name of the
> > LOCAL_MODULE to libsensors, and is this the expected library that
> > gets loaded from /system/lib at runtime?
> >
> > Also, if I install a complete base build on a test system/phone, can I
> > then make changes to sensors.c, rebuild the library, and drop it into
> > /system/lib before startup?
> >
> > thanks again for your help.
> > John
> >
> > On Mon, Aug 16, 2010 at 7:47 AM, John Koshi <[email protected]> wrote:
> >
> >     Frank,
> >
> >     I checked the make file in the libsensors directory, and found that
> >     LOCAL_MODULE_PATH was set to "optional". I changed it to "user",
> >     and ran "make sensors.mahimahi" from the source tree root. It built
> >     out/target/product/generic/system/lib/hw/sensors.mahimahi.so. Is
> >     this the expected result? I had expected a libsensors.so file. Is
> this
> >     dependent on the name in LOCAL_MODULE?
> >
> >     Also, I was unable to find a commit version for the Android.mk file.
> I
> >     was probably not looking in the right place for it.
> >
> >     thanks,
> >     John
> >
> >
> >     On Sun, Aug 15, 2010 at 7:02 PM, John Koshi <[email protected]>
> wrote:
> >
> >         Hi Frank,
> >
> >         I did exactly those steps for the build. I'll look at the
> cookbook and see
> >         if the setting on the libsensor is set to "optional". If it is
> I'll change it from
> >         "optional" to "user" (I assume that's right), and check the build
> again.
> >
> >         Regarding the second part, the Android.mk file in the sensors
> directory
> >         has "LOCAL_MODULE := sensors.mahimahi". I am unable to check the
> >         version on the makefile right now, but will let you know as soon
> as I can.
> >         I did the repo sync just the day before yesterday, so it should
> have got
> >         the latest files as of then.
> >
> >         thanks
> >
> >
> >         On Sun, Aug 15, 2010 at 6:20 PM, Frank Maker <
> [email protected]> wrote:
> >
> >             Hello John,
> >
> >             (I am replying to you here so others can reference this
> thread.)
> >
> >             First of all, I assume you did build/envsetup.sh, a recent
> "repo sync"
> >             and cleaned your build. The problem may be that the libsensor
> module
> >             (in that directory's Android.mk) is set to "optional" which
> from the
> >             build cookbook (
> http://source.android.com/porting/build_cookbook.html)
> >             may keep it from being built. In this case, you could try
> changing it
> >             to something like "user".
> >
> >             Secondly, if the Android.mk specifies "LOCAL_MODULE :=
> >             sensors.mahimahi" then that make command should find the
> makefile and
> >             run it. I see cb68a916 as my commit version for that
> makefile, do you
> >             see this version as well? (
> http://android.git.kernel.org/?p=device/htc/
> >             passion-common.git;a=blob;f=libsensors/
> >
> Android.mk;h=a9bc91e709e6b1fe980d8c43032032be200191dc;hb=22c624876354cfd753aad05c166f2389f092dd2b).
> >
> >             -Frank
> >
> >             On 08/15/2010 03:13 PM, John Koshi wrote:
> >             > Hi Frank,
> >             >
> >             > Thanks for the feedback. However, on doing your first step,
> libsensors
> >             > did not get built, although the build completed
> successfully. Then when
> >             > I ran "make sensors.mahimahi", I got the two messages:
> >             >
> >             > No private recovery resources for TARGET_DEVICE passion"
> >             > make: Nothing to be done for 'sensors.mahimahi'.
> >             >
> >             > Do you know what could be causing these errors.
> >             >
> >             > thanks
> >
> >
> >             On Aug 15, 8:03 am, Frank Maker <[email protected]>
> wrote:
>  >             > If you setup your environment ( ". build/envsetup.sh"
> from
> >             > $ANDROID_ROOT) and then run "lunch" and select the passion
> one, it
> >             > should build. If that doesn't work for some reason, from
> the root
> >             > directory just use the variable "LOCAL_MODULE" from the
> libsensors
> >             > Makefile. So in this case it would be "make
> sensors.mahimahi".
> >             >
> >             > Hope that helps ;-)
> >             >
> >             > -Frank
> >             >
> >             > On Aug 14, 5:14 pm, nature lover <[email protected]>
> wrote:
> >             >
> >             >
> >             >
> >             > > Hello,
> >             >
> >             > > In doing a complete rebuild of the froyo 2.2 source tree,
> I did not
> >             > > find libsensors.so as having been built. Any one know
> why?
> >             >
> >             > > Also, if I were to modify sensors.c located at
> device/htc/passion-
> >             > > common/libsensors/, what is the best way to rebuild just
> the library
> >             > > libsensors.so, and test the changes?
> >             >
> >             > > thanks
> >
> >
> >
>
> --
> unsubscribe: 
> [email protected]<android-porting%[email protected]>
> website: http://groups.google.com/group/android-porting
>

-- 
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting

Reply via email to