From owner-freebsd-chromium@FreeBSD.ORG Wed Feb 5 21:33:34 2014 Return-Path: Delivered-To: chromium@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 BC4BF8DA; Wed, 5 Feb 2014 21:33:34 +0000 (UTC) Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 583331C54; Wed, 5 Feb 2014 21:33:34 +0000 (UTC) Received: by mail-ob0-f171.google.com with SMTP id wp4so1191753obc.30 for ; Wed, 05 Feb 2014 13:33:33 -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 :cc:content-type; bh=MvaV1Tn8IKm5tcV7BFGHMhIAa79N5j0juKadPhjYAp0=; b=kk8irH0Yvh9yr+qD4t075vDn2B30/hOsw2QJkMXc2g5ZJo8MCWPJDWx3enus9oiP0q xO+Xpt+Is9XEpZEO96sf4WW4UcJJrEDWnUUbEl4cpqKuyLPu/kGbuIG4wEHMUtyznQeV unjm7OkbxWOXMbX17THIweEMY6pmadQZFDyq3C/vHZXwfrAloc7LgItC9xCti7MQSpRf UZj2KQsSnBUatUP9QmPBcaMF4Cwyk0OrH0OSieJAyaSWcJqeVrPstx+H/pQn7sr4Lw5j JHlRT6tr0CZlPeZrF+WOUUZLvteLVY0f96JUfCFR5ctk8rKvgUbICymbKg+0JMI4Xh2R 9yZw== MIME-Version: 1.0 X-Received: by 10.60.62.199 with SMTP id a7mr3345225oes.64.1391636013600; Wed, 05 Feb 2014 13:33:33 -0800 (PST) Received: by 10.182.78.71 with HTTP; Wed, 5 Feb 2014 13:33:33 -0800 (PST) In-Reply-To: References: Date: Wed, 5 Feb 2014 16:33:33 -0500 Message-ID: Subject: Re: Making WebRTC available for FreeBSD From: Joe Nosay To: Niklas Enbom Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: ports , Jan Linden , Adrian Chadd , chromium@freebsd.org, gecko@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Feb 2014 21:33:34 -0000 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?