List Info

Thread: Building splay_audio_all




Building splay_audio_all
user name
2008-04-25 08:49:26
Hi,

Could you please advise which BIF branch, targets and
profiles can be
used to make a command line audio player (splay) to play
mp3, aacplus,
real and wma (I have licenses for those codecs)?

I am building it in following two platforms respectively:

(1) Debian box where SYSTEM_ID=linux-2.2-libc6-gcc32-i586;

(2) A mobile ARM processor.


Thank you.

Kind Regards.

Jim

_______________________________________________
Helix-client-dev mailing list
Helix-client-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev

RE: Building splay_audio_all
country flaguser name
United States
2008-04-25 07:35:33
For linux-2.2-libc6-gcc32-i586, I would do the
following build:

BIF:     hxclient_3_1_0_atlas_restricted
target:  splay
profile: helix-client-all-defines

For the ARM platform, I don't know which
BIF/branch is best.

Eric
 
=============================================
Eric Hyche (ehychereal.com)
Technical Lead
RealNetworks, Inc.  

> -----Original Message-----
> From: helix-client-dev-bounceshelixcommunity.org 
> [mailto:helix-client-dev-bounceshelixcommunity.org] On 
> Behalf Of jupiter.hcegmail.com
> Sent: Friday, April 25, 2008 9:49 AM
> To: helix-client-devhelixcommunity.org
> Subject: [Helix-client-dev] Building splay_audio_all
> 
> Hi,
> 
> Could you please advise which BIF branch, targets and
profiles can be
> used to make a command line audio player (splay) to
play mp3, aacplus,
> real and wma (I have licenses for those codecs)?
> 
> I am building it in following two platforms
respectively:
> 
> (1) Debian box where
SYSTEM_ID=linux-2.2-libc6-gcc32-i586;
> 
> (2) A mobile ARM processor.
> 
> 
> Thank you.
> 
> Kind Regards.
> 
> Jim
> 
> _______________________________________________
> Helix-client-dev mailing list
> Helix-client-devhelixcommunity.org
> http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev
> 


_______________________________________________
Helix-client-dev mailing list
Helix-client-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev

Re: Building splay_audio_all
user name
2008-04-26 15:21:32
On 2008-04-25 08:35-0400, Eric Hyche wrote:
>
>For linux-2.2-libc6-gcc32-i586, I would do the
>following build:
>
>BIF:     hxclient_3_1_0_atlas_restricted
>target:  splay
>profile: helix-client-all-defines

That's built well without errors on my Debian box. I had an
initial test for different codecs, mp3 and aacplus seems
fine, but tested on real and wma audio had
following error:

Report(3, -2147221487, "(NULL)", 0,
"(NULL)", "HXR_NO_RENDERER")

What was I missing?

>For the ARM platform, I don't know which
>BIF/branch is best.

What are the differences between
hxclient_3_1_0_atlas_restricted and
hxclient_2_2_1_cayennes_restricted? If possible, please
point me a document to explain rules and current status in
different BIF branches.

Thanks Eric,

Kind Regards.


_______________________________________________
Helix-client-dev mailing list
Helix-client-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev

what libraries needed to get splay working
user name
2008-04-28 12:06:58
Hi

I am trying to get familiar with Helix Client for the first
time and
wanted to compile and run splay test player. I used ribosome
build to
checkout sources for atlast_3_1_0, I can compile the source
and there
are some modules that don't compile. Splay compiles ok. I am
trying to
run splay binary on FC8 host, and with libraries that I
compile, I
cannot get the player to work (just returns), but with
nightly build
libraries(all_clients-hxclient_3_1_0_atlas-20080427-linux-2.
2-libc6-gcc3
2-i586), the player works fine (using my build splay
binary). So there
are some libraries that are missing on my side. How can I
see what is
needed by splay. Is it suppose to work for Fedora Core8
side?
SYSTEM_ID=linux-2.6-glibc23-i686 is used.

#python /root/helix/build/bin/build.py -m
hxclient_3_1_0_atlas -P
helix-client-all-defines splay

Associated build.out is included.


Thanks
naeem

_______________________________________________
Helix-client-dev mailing list
Helix-client-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev

  
Re: what libraries needed to get splay working
country flaguser name
United States
2008-04-30 18:31:15
Afzal, Naeem M wrote:
> Hi
>
> I am trying to get familiar with Helix Client for the
first time and
> wanted to compile and run splay test player. I used
ribosome build to
> checkout sources for atlast_3_1_0, I can compile the
source and there
> are some modules that don't compile. Splay compiles ok.
I am trying to
> run splay binary on FC8 host, and with libraries that I
compile, I
> cannot get the player to work (just returns), but with
nightly build
>
libraries(all_clients-hxclient_3_1_0_atlas-20080427-linux-2.
2-libc6-gcc3
> 2-i586), the player works fine (using my build splay
binary). So there
> are some libraries that are missing on my side. How can
I see what is
> needed by splay. Is it suppose to work for Fedora Core8
side?
> SYSTEM_ID=linux-2.6-glibc23-i686 is used.
>
> #python /root/helix/build/bin/build.py -m
hxclient_3_1_0_atlas -P
> helix-client-all-defines splay
>
> Associated build.out is included.
>
>   

If you search for the following section in Helix Player
QuickStart, you 
will find some troubleshooting guide:
https://player.helixcommunity.org/2007/dev/quickstart.
html


        Troubleshooting Build Failure:


This is what I see in your build.out file.

entering directory protocol/rtsp
UNIXCompile(protocol/rtsp): making copy
make copy
make  SUBMAKEFLAGS="" -f rtsplib.mak copy
make[1]: Entering directory
`/root/helix/splay-atlas-3-1-0/protocol/rtsp'
make[1]: Nothing to be done for `copy'.
make[1]: Leaving directory
`/root/helix/splay-atlas-3-1-0/protocol/rtsp'
make  SUBMAKEFLAGS="" -f rtspclntdll.mak copy
make[1]: Entering directory
`/root/helix/splay-atlas-3-1-0/protocol/rtsp'


make[1]: *** No rule to make target 
`/root/helix/splay-atlas-3-1-0/protocol_dist/rtsp/dbg/rdtcln
tlib.a', 
needed by `dbg/rtspclnt.so'.  Stop.


make[1]: Leaving directory
`/root/helix/splay-atlas-3-1-0/protocol/rtsp'
make: *** [copy] Error 2
Time used: 0.04 seconds
ERROR: UNIXCompile(protocol/rtsp) ERROR: Make failed.

--- Build System Error ------------------------------------
Make failed.
-----------------------------------------------------------

Looks like you haven't accepted the BEULA (Binary EULA) to
check out 
distribution binaries:
https://helixcommun
ity.org/beula/

-- 
Daniel Yek.


> Thanks
> naeem
>   
>   

_______________________________________________
Helix-client-dev mailing list
Helix-client-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev

RE: what libraries needed to get splay working
user name
2008-04-30 18:36:50
Actually I tried different SYSTEM_ID and checked out fresh
source tree.
Compilation went OK and also I was able to play splay
binary.

Export SYSTEM_ID=linux-2.2-libc6-gcc32-i586.

Regards

naeem

>-----Original Message-----
>From: Daniel Yek [mailto:dyekreal.com]
>Sent: Wednesday, April 30, 2008 4:31 PM
>To: Afzal, Naeem M
>Cc: helix-client-devhelixcommunity.org
>Subject: Re: [Helix-client-dev] what libraries needed to
get splay
working
>
>
>Afzal, Naeem M wrote:
>> Hi
>>
>> I am trying to get familiar with Helix Client for
the first time and
>> wanted to compile and run splay test player. I used
ribosome build to
>> checkout sources for atlast_3_1_0, I can compile
the source and there
>> are some modules that don't compile. Splay compiles
ok. I am trying
to
>> run splay binary on FC8 host, and with libraries
that I compile, I
>> cannot get the player to work (just returns), but
with nightly build
>>
libraries(all_clients-hxclient_3_1_0_atlas-20080427-linux-2.
2-libc6-gcc3
>> 2-i586), the player works fine (using my build
splay binary). So
there
>> are some libraries that are missing on my side. How
can I see what is
>> needed by splay. Is it suppose to work for Fedora
Core8 side?
>> SYSTEM_ID=linux-2.6-glibc23-i686 is used.
>>
>> #python /root/helix/build/bin/build.py -m
hxclient_3_1_0_atlas -P
>> helix-client-all-defines splay
>>
>> Associated build.out is included.
>>
>>
>
>If you search for the following section in Helix Player
QuickStart, you
>will find some troubleshooting guide:
>https://player.helixcommunity.org/2007/dev/quickstart.
html
>
>
>        Troubleshooting Build Failure:
>
>
>This is what I see in your build.out file.
>
>entering directory protocol/rtsp
>UNIXCompile(protocol/rtsp): making copy
>make copy
>make  SUBMAKEFLAGS="" -f rtsplib.mak copy
>make[1]: Entering directory
`/root/helix/splay-atlas-3-1-0/protocol/rtsp'
>make[1]: Nothing to be done for `copy'.
>make[1]: Leaving directory
`/root/helix/splay-atlas-3-1-0/protocol/rtsp'
>make  SUBMAKEFLAGS="" -f rtspclntdll.mak copy
>make[1]: Entering directory
`/root/helix/splay-atlas-3-1-0/protocol/rtsp'
>
>
>make[1]: *** No rule to make target
>`/root/helix/splay-atlas-3-1-0/protocol_dist/rtsp/dbg/rd
tclntlib.a',
>needed by `dbg/rtspclnt.so'.  Stop.
>
>
>make[1]: Leaving directory
`/root/helix/splay-atlas-3-1-0/protocol/rtsp'
>make: *** [copy] Error 2
>Time used: 0.04 seconds
>ERROR: UNIXCompile(protocol/rtsp) ERROR: Make failed.
>
>--- Build System Error
------------------------------------
>Make failed.
>--------------------------------------------------------
---
>
>Looks like you haven't accepted the BEULA (Binary EULA)
to check out
>distribution binaries:
>https://helixcommun
ity.org/beula/
>
>--
>Daniel Yek.
>
>
>> Thanks
>> naeem
>>
>>

_______________________________________________
Helix-client-dev mailing list
Helix-client-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev

[1-6]

about | contact  Other archives ( Real Estate discussion Medical topics )