Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[B2G] Try Server: Build Error on WebRTC according New nsString Attribute on nsAudioStream

12 views
Skip to first unread message

Marco Chen

unread,
Oct 19, 2012, 6:10:43 AM10/19/12
to dev-...@lists.mozilla.org, Matthew Gregan
Dear all,

May I know who is the contact window for build issue related to WebRTC feature?

Recently I worked on bug 795237, and planed to add a nsString attribute into nsAudioStream class.
nsAudioStream will translate this nsSting to char * then pass to external audio library.
But when I push it to try server, I found WebRTC seems directly use nsAudioStream in external linkage code.
So there will be compile errors.

May be these caused by my fault but I want to discuss with contact window for this issue?

https://tbpl.mozilla.org/php/getParsedLog.php?id=16224502&tree=Try&full=1

Thanks,
Sincerely yours.

-------------------------------------
Marco Chen
Senior SW Engineer
Mozilla Taiwan

Tel: +886-2-87861100 # 352
mail: mc...@mozilla.com

Randell Jesup

unread,
Oct 19, 2012, 12:02:28 PM10/19/12
to dev-...@lists.mozilla.org
On 10/19/2012 6:10 AM, Marco Chen wrote:
> May I know who is the contact window for build issue related to WebRTC feature?
>
> Recently I worked on bug 795237, and planed to add a nsString attribute into nsAudioStream class.
> nsAudioStream will translate this nsSting to char * then pass to external audio library.
> But when I push it to try server, I found WebRTC seems directly use nsAudioStream in external linkage code.
> So there will be compile errors.
>
> May be these caused by my fault but I want to discuss with contact window for this issue?
>
> https://tbpl.mozilla.org/php/getParsedLog.php?id=16224502&tree=Try&full=1

The best thing to do for this sort of problem is to file a bug. Then
(for webrtc issues), you can try asking in #media.

In this case, you've added code that requires internal libxul linkage to
classes used from the C++ unit tests. You can turn them off (they
default to off for now, but will be turned on), or you can #ifdef your
changes using #ifdef MOZILLA_INTERNAL_API

Randell Jesup
0 new messages