Re: Linux platform: splay client for AAC and HE-AAC codecs

Stephane Turlier wrote:
> Thanks for your reply Greg,
>
> Unfortunately, such settings won't build on my configuration (I tried both
> helix and cayenne 1_5_0 branches). Actually most of the image and video
> modules won't build and I had very little time today to investigate on it.
>   

Hi Stephane,

We usually encourage developers to get over the problems of building 
with these settings though. Getting through that could probably resolves 
the problem, yourself.

> Besides I am for the moment more interested in the audio modules (that do
> build and work since I achieved playback of mp3 and ra).
>
> However, I have some questions: is it normal that the splay_audio_all does
> not have support for aac or is-it just my config that does not build it
> properly?
>   

Are raac.so, mp4arender.so, and mp4fformat.so getting built? If so, AAC 
and HE-AAC support should probably be there.

(I don't see raac.so, nor mp4*.so, in your initial post. That might be 
the problem. Also you mentioned building datatype_mp4_audio_renderer, 
but that probably didn't include the decoder -- I didn't check when I'm 
typing this out.)

If not, and if you would like, you can investigate into building 
aacff.so if it helps. Also, read to the bottom of my response.

> I am using the system variable SYSTEM_ID= linux-2.2-libc6-gcc32-i586 as
> indicated in the quick start tutorial. 
> But I am actually running a Fedora
> Core 9 with linux-2.6 and gcc 4.3! Is-it part of the reason? Does any-one
> use such development environment and could give some feedback?
>   

This:
SYSTEM_ID=linux-2.2-libc6-gcc32-i586
is the right setting for Linux (x86 machine, of course) for most cases. 
In fact, most of the time other SYSTEM_ID simply won't work well, 
because of the existence of some SYSTEM_ID specific .pcf files and more 
importantly the availability of distribution binaries for the SYSTEM_ID.

Think of it that the SYSTEM_ID requires Linux 2.2 and continues to work 
for Linux 2.6. There is some amount of work to change the SYSTEM_ID to 
be more intuitive, but for no much any other gain.

When working with systems with selinux turned on, such as Fedora, it is 
essential to make sure that selinux isn't preventing the .so files and 
the application from being loaded.

Running the following command after every build usually solves the 
selinux problem (quick and dirty):
chcon -t texrel_shlib_t *.so

I know that raac.so file is linked with some object files not compiled 
with -fPIC and thus is causing problems with selinux. So, apply chcon 
command above on it as the minimum.

I think the most sensible thing for us to do is to integrate the selinux 
chcon support into Ribosome, the Helix build system, so that developers 
don't need to be aware of selinux problem or have to install the product 
built so that the product can handle chcon operations during 
installation. I'll have to do that much later when I have the time, 
unless someone submit a patch.

-- 
Daniel Yek.



> Regards,
>
> Stephane.
>
>
> On Wed, 24 Sep 2008 10:18:57 -0700, Greg Wright <[email protected]> wrote:
>   
>> Not AAC specific, but, by *far* the best combination to build is:
>>
>>    splay
>>    helix-client-all-defines
>>
>> That is the largest build, but includes support for
>> everything. It is also tested the most. Once that works
>> for you, you can then start parsing down the build if
>> needed. There are so many combinations available to build
>> splay that some don't always work if they have not been
>> built/used by anyone in a long time.
>>
>> --greg.
>>
>>
>>
>> Stephane Turlier wrote:
>>     
>>> Hello,
>>>
>>> I come again to you because I am having a hard time to have the aac
>>> playback on a simple player client on Linux. I tried to do it this way.
>>>
>>>     * I build with ribosome a splay_audio_all client based on the
>>>       
>> cayenne
>>     
>>> 1_5_0 branche, and I save the files compiled in the \debug folder to
>>> another folder, lets call it \splay_player. This splay_audio_all client
>>>       
>> is
>>     
>>> able to playback mp3s and ras but no m4a file. Indeed it does not have
>>>       
>> the
>>     
>>> libraries for it. 
>>>
>>>     * I build with ribosome a  datatype_mp4_audio_renderer and I copy
>>>       
>> the
>>     
>>> compiled files to my \splay_player folder.
>>>
>>> But still, my splay player won't play my m4a files (using aac codec).
>>>
>>> I think I am missing something (like building dependencies, etc), but I
>>> can't see what, I am really stuck.
>>>
>>> Thanks in advance for your answers.
>>>
>>> Regards,
>>>
>>> Stephane.
>>>       

_______________________________________________
Helix-client-dev mailing list
[email protected]
http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev