Hi Deva,

In the directory, out/target/product/generic/obj/SHARED_LIBRARIES/
libxxx_intermediates, there were two files - xxx.o and xxx.P, but no
LINKED directory and libxxx.so. I guess my Android.mk was picked but
my library was not completely built.

In opencore related header file, I included my own header file and
declared an object named m_MySync. Its type is MySync that was defined
in my header file. But, when making whole system, I got following
error message:

error: 'MySync' does not name a type.

Actually, I tested this library in frameworks media player, and it
worked fine. But in opencore, it seems not workable. Do you have any
idea about this problem?

BTW, thanks for replying me.


On Jul 14, 2:55 am, Deva R <r.deva...@gmail.com> wrote:
> >I would like to add my own shared library in Android opencore
> >protocol, but I got some error messages when making whole system.
>
> Can you elaborate on what you did, and what error u got??
>
> probably Android.mk of ur library is not picked at first place, during
> build.,
>
> On Tue, Jul 13, 2010 at 2:55 PM, Harry C. <hyc...@gmail.com> wrote:
> > I would like to add my own shared library in Android opencore
> > protocol, but I got some error messages when making whole system.
> > After checking the following directory: out/target/product/generic/obj/
> > SHARED_LIBRARIES/libxxx_intermediates, I found out there was no
> > libxxx.so, even it's already added in prelinkmap. I am not sure the
> > reason but guess that might be because my library wasn't built yet
> > when system needed it to make opencore library. So, does any one can
> > give me suggestion to solve this problem? like how to modify the make
> > file to force system built my library earlier than opencore?
>
> > --
> > unsubscribe: 
> > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com>
> > website:http://groups.google.com/group/android-porting
>
>

-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

Reply via email to