Hi Rktp,

When I try the same in the quick_start file. I am geeting a error when
building the make -j.

When I make -j, am geeting the follwoing error, So can anyone help me
out to solve this error.


--------------------------------------------------------------------------------------------------


Building /home/android/mydroid/external/opencore/build_config/
opencore_dynamic/build/installed_lib/linux/
libopencore_mp4local_debug.so...

DONE building /home/android/mydroid/external/opencore/build_config/
opencore_dynamic/build/installed_lib/linux/
libopencore_mp4local_debug.so.

Building /home/android/mydroid/external/opencore/build_config/
opencore_dynamic/build/engines/player/test/build/android/linux/
test_pv_player_engine.o

Using /home/android/mydroid/external/opencore/engines/player/test/src/
test_pv_player_engine.cpp
cc1plus: warnings being treated as errors
/home/android/mydroid/external/opencore/engines/player/test/src/
test_pv_player_engine.cpp: In function ‘int _local_main(FILE*,
cmd_line*)’:

/home/android/mydroid/external/opencore/engines/player/test/src/
test_pv_player_engine.cpp:1878: error: format not a string literal and
no format arguments

make: *** [/home/android/mydroid/external/opencore/build_config/
opencore_dynamic/build/engines/player/test/build/android/linux/
test_pv_player_engine.o] Error 1

andr...@android-desktop:~/mydroid/external/opencore/build_config/
opencore_dynamic$ make run_pe_test TEST_ARGS="-help"
/home/android/mydroid/external/opencore/tools_v2/build/make/library.mk:
53: warning: overriding commands for target `/home/android/mydroid/
external/opencore/build_config/opencore_dynamic/build/
installed_include/getactualaacconfig.h'

/home/android/mydroid/external/opencore/tools_v2/build/make/library.mk:
53: warning: ignoring old commands for target `/home/android/mydroid/
external/opencore/build_config/opencore_dynamic/build/
installed_include/getactualaacconfig.h'

Building /home/android/mydroid/external/opencore/build_config/
opencore_dynamic/build/engines/player/test/build/android/linux/
test_pv_player_engine.o

Using /home/android/mydroid/external/opencore/engines/player/test/src/
test_pv_player_engine.cpp
cc1plus: warnings being treated as errors
/home/android/mydroid/external/opencore/engines/player/test/src/
test_pv_player_engine.cpp: In function ‘int _local_main(FILE*,
cmd_line*)’:

/home/android/mydroid/external/opencore/engines/player/test/src/
test_pv_player_engine.cpp:1878: error: format not a string literal and
no format arguments

make: *** [/home/android/mydroid/external/opencore/build_config/
opencore_dynamic/build/engines/player/test/build/android/linux/
test_pv_player_engine.o] Error 1




--------------------------------------------------------------------------------------------------


On Apr 3, 5:49 pm, sonal gupta <sonal.aqua.gu...@gmail.com> wrote:
> THe .cfg file should be present in the same directory as your
> pvplayer_engine_test application .
> The application will pick it at run time to register the OMX Core.
> You can find it in the opencore/  directory.
>
> Regards,
> Sonal
>
>
>
> On Fri, Apr 3, 2009 at 3:46 PM, renu <ren...@gmail.com> wrote:
> > Hi Sonal,
>
> > In one of the mail chains you had mentioned that the pvplayer.cfg file
> > has to be kept in our working directory.
>
> > I'm trying to run PV OpenCore test cases out of Android as there seem
> > to issues with RTSP streaming on emulator.
>
> > Can you tell me what has to be done with the ".cfg" file .where do
> > have to take it from and where do we have to keep it?
>
> > Thanks,
> > Renu- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"android-framework" group.
To post to this group, send email to android-framework@googlegroups.com
To unsubscribe from this group, send email to 
android-framework+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/android-framework?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to