Re: how to deal with DEFINE option when two modules requirement are different in one target?

Gregory Wright <[email protected]> Tue, 22 Sep 2009 09:41:21 -0700
Newsgroups gmane.comp.multimedia.helix.devel
Message-ID <[email protected]>
On Sep 21, 2009, at 5:31 PM, Zhao, Halley wrote:

>
> I saw HELIX_CONFIG_BLT_ONLY_ON_GTK_THREAD in helix-client-moblin.pf,  
> and it takes effect in basesurf.cpp etc. I don't know who add it.
>
> You mean I could remove it from helix-client-moblin.pf?

No, someone put it there for a reason. I am just saying that the Helix  
Platform
can work just fine without GTK. You can look at the annotations 'cvs  
ann' for
that file and see who added it and ask them. Perhaps it can be removed  
or you
can create a new .pf file for your product that doesn't use GTK.


--greg.



> BR
>
>
> -----Original Message-----
> From: Gregory Wright [mailto:[email protected]]
> Sent: 2009年9月21日 22:47
> To: Zhao, Halley
> Cc: '[email protected]'
> Subject: Re: [Helix-client-dev] how to deal with DEFINE option when  
> two modules requirement are different in one target?
>
> On Sep 21, 2009, at 2:23 AM, Zhao, Halley wrote:
>
>> For example target player includes libraries: hxmedplyeng.so and
>> hxmediasink.so
>>
>> Hxmedplyeng.so requires HELIX_CONFIG_BLT_ONLY_ON_GTK_THREAD
>> hxmediasink.so conflicts with HELIX_CONFIG_BLT_ONLY_ON_GTK_THREAD,
>> because it needs GTK support.
>
> What exactly is your question?
>
> Why do you say that HXMedpPlayEng.so *requires*
> HELIX_CONFIG_BLT_ONLY_ON_GTK_THREAD, it
> does not, or should not.
>
> --greg.
>
>>
>> Then how could I achieve this?
>> BR
>> ZHAO, Halley (Aihua)
>> Email: [email protected]
>> Tel: +86(21)61166476
>> iNet: 8821-6476
>> SSG/OTC/Moblin 3W038 Pole: F4
>>
>> _______________________________________________
>> Helix-client-dev mailing list
>> [email protected]
>> http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev
>