From owner-freebsd-gecko@FreeBSD.ORG Wed Feb 5 21:58:18 2014 Return-Path: Delivered-To: gecko@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CBC4939E; Wed, 5 Feb 2014 21:58:18 +0000 (UTC) Received: from mail-oa0-x232.google.com (mail-oa0-x232.google.com [IPv6:2607:f8b0:4003:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 70C721E19; Wed, 5 Feb 2014 21:58:18 +0000 (UTC) Received: by mail-oa0-f50.google.com with SMTP id n16so1283777oag.23 for ; Wed, 05 Feb 2014 13:58:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=M0uTG1CsQIahedbhJxhEWR4e7K6mlurJ25q+LhSefMs=; b=saWKpwEwzxSmbduAMyLAq9wGUkW77Apw0U1gE4YFcRWX5UngjEtIfLWRZSdBr2h2Rj aLT9MF3bjOn81+8NNmWbFrLa5XW3b6eLO138lruBVjZb8HofqfVAosxJLkHah0ujWFDu mJTm184S5lW2EuGX0yLw3vYNkImlPcZK2o90np2TeINMXbRwr3R8+/NdR4uomPgzqgMQ uv9VHvv0SlK64ELm57Qb7Y8RH6YjIeqj5wKgtVHE3Er5qDJErNbpNBG86m3OpwqCJIys PWU5cvfOFXxpNDWhKB29CYW7LuOdvK3INZkgOIQe90HsmhzJwvEV4Ru2+2jE7c/eUOmn bwCA== MIME-Version: 1.0 X-Received: by 10.182.33.73 with SMTP id p9mr3418405obi.37.1391637497734; Wed, 05 Feb 2014 13:58:17 -0800 (PST) Received: by 10.182.78.71 with HTTP; Wed, 5 Feb 2014 13:58:17 -0800 (PST) In-Reply-To: References: Date: Wed, 5 Feb 2014 16:58:17 -0500 Message-ID: Subject: Re: Making WebRTC available for FreeBSD From: Joe Nosay To: Niklas Enbom , Adrian Chadd , gecko@freebsd.org, chromium@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-gecko@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Gecko Rendering Engine issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Feb 2014 21:58:18 -0000 On Wed, Feb 5, 2014 at 4:44 PM, Niklas Enbom wrote: > I still don't get what you mean. WebRTC is a part of browsers (Chrome, > Firefox) not the operating system. Are you looking for a browser that runs > on freeBSD and supports WebRTC - or something else? > > > On Wed, Feb 5, 2014 at 1:36 PM, Joe Nosay wrote: > >> >> >> >> On Wed, Feb 5, 2014 at 4:33 PM, Joe Nosay wrote: >> >>> >>> >>> >>> On Wed, Feb 5, 2014 at 4:27 PM, Niklas Enbom wrote: >>> >>>> Hey guys, not sure what this refers to. The G+ post talks about porting >>>> the gtalk plugin to freeBSD. WebRTC is an effort in the opposite direction >>>> (no plugins needed). Afaik there is a Chromium build for freeBSD that >>>> should support WebRTC (unless it's disabled at build). >>>> >>>> Niklas >>>> >>>> >>>> On Wed, Feb 5, 2014 at 1:14 PM, Joe Nosay wrote: >>>> >>>>> https://plus.google.com/110946378055202199166/posts/8iTsSCatk4x >>>>> >>>>> The process has been started : >>>>> http://forums.freebsd.org/viewtopic.php?f=39&t=44691 >>>>> >>>>> Dependencies needed- referenced in "howto" and webrtc dependencies: >>>>> libbrlapi from brltty. >>>>> >>>>> >>>>> Benefits: Native client and sever side of WebRTC applications for >>>>> FreeBSD and possibly other BSDs. >>>>> Eliminated dependency for Linuixlator based applications thus cutting >>>>> down on hardware resource use. >>>>> Eliminated need for other simulated and emulated programs to run Skype >>>>> or other voice-and-video binaries. I.e. Wine, VirtualBox, qemu, et cetera, >>>>> et al. >>>>> >>>>> Since it is known that Sony's PS4 uses FreeBSD as the basis for its >>>>> OS, WebRTC could be implemented as a native application on the >>>>> platform/console thus allowing users to communicater in real time while >>>>> gaming. >>>>> >>>>> >>>>> Why am I proposing this? >>>>> 1. Adrian Chadd asked on Google+ and nowhere else. I decided to bring >>>>> his proposal to the public and attempt an initial starting phase. >>>>> 2. Users would not be limited to having only a few selected operating >>>>> systems at their disposal. Developers could easily communicate with each >>>>> other. >>>>> 3. Real time sharing/viewing of conventions. This would give the >>>>> community another window into the development of FreeBSD. >>>>> 4. Companies such as IxSystems and Sony would be able to contact >>>>> develoers while simultaneously working on a FreeBSD/FreeBSD_based system. >>>>> 5. FreeBSD developers would be able to give feedback on the >>>>> development of WebRTC sources. >>>>> >>>>> >>>>> >>>>> Being that I am limited on resources, is it possible that others could >>>>> take over what was started? >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>> >>> How is it implemented at build time? >>> >> >> The option is not available with make config on FreeBSD nor is brltty >> available on FreeBSD. The gyp files do not include any FreeBSD specific >> references. >> > > WebRTC will only work if it can be built natively on a system despite the browser type. In trunk/build/ there are the following operating systems: android, ios, linux, mac, win. Also, the jingle protocol has not been ported to FreeBSD. Are there any developers who use FreeBSD? Anyway, I was hoping that maybe someone much better than me in/with programming and the FreeBSD community would see the benefits of bringing this to FreeBSD and take over my efforts. My initial arguments for such are in the first email of this thread.