From owner-freebsd-chromium@FreeBSD.ORG Tue Mar 11 01:05:40 2014 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B111F671; Tue, 11 Mar 2014 01:05:40 +0000 (UTC) Received: from mail-oa0-x22a.google.com (mail-oa0-x22a.google.com [IPv6:2607:f8b0:4003:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 57D2696D; Tue, 11 Mar 2014 01:05:40 +0000 (UTC) Received: by mail-oa0-f42.google.com with SMTP id i4so7820945oah.15 for ; Mon, 10 Mar 2014 18:05:39 -0700 (PDT) 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=lc+IHKh4BFlzaf5d0HuOwm5g6kpPiF9NUe71tTOUjrI=; b=diZZ/woQ4PQ7TqraEDQpYcBpixOF7y+K0lTWtBdjGj8TVOv1xK1M2xbcaaNgKtSyV7 jyjjsg/fUyThW8AYAJID/gLhjuXDrQcznF80PDWLG+sPM3TbPEodHNAkxp424coXQYE9 YwqfOb3KjFGGK1FdstpSIuFtVX9tPcnLfiBL2wMQInfM19czN1hKcUqco+gmaiCInOsp JYw9aJbJDmNv2+/tEdQit5KNUqJMwc95V0+yXkvz8GLxQKihiJWgoMnDcE1MxTGl/XlP Vh4JMJykNju5Bb1iwWJzwO8H7W7MRXKiyyIIRlhHR5zonQZ0Adcqt5lL2O0LQwDUnlAV qkxw== MIME-Version: 1.0 X-Received: by 10.182.28.134 with SMTP id b6mr30998043obh.27.1394499939762; Mon, 10 Mar 2014 18:05:39 -0700 (PDT) Received: by 10.182.76.201 with HTTP; Mon, 10 Mar 2014 18:05:39 -0700 (PDT) In-Reply-To: References: Date: Mon, 10 Mar 2014 21:05:39 -0400 Message-ID: Subject: Re: Making WebRTC available for FreeBSD From: Joe Nosay To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: chromium@freebsd.org, gecko@freebsd.org, Niklas Enbom 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: Tue, 11 Mar 2014 01:05:40 -0000 On Mon, Mar 10, 2014 at 9:04 PM, Adrian Chadd wrote: > Are you interested in just dumping all of the stuff you're discovering > into a blog, so it can be a journey? > > > -a > > On 10 March 2014 18:03, Joe Nosay wrote: > > > > > > > > On Sat, Feb 8, 2014 at 5:26 AM, Joe Nosay > wrote: > >> > >> I know that by reading the files in > >> webrtc_source/trunk/webrtc/modules/audio_device that a freebsd folder > needs > >> to be located there. The linux system shows control of the audio through > >> pulse and alsa . What should be located there are the files > referencing the > >> proper parts of system, phonon, gstreamer, esound, and others. If I > had a > >> nother computer with Linux on it, I would compare the references to the > >> files in trunk/build/webrtc/modules/audio_device/linux to what would be > the > >> equivalent on FreeBSD. The linux files would then be used as a > template to > >> create the freebsd ones. > >> What are the freebsd base system h files needed? Reference them at a new > >> folder. Which sound severs? Another reference. > >> > >> There is a command using find and grep to print out files which contain > an > >> exact phrase. I t is not " find /$PATH -exec grep -H -E -o "PATTERN" {} > \;" > >> > >> > >> > >> > >> > >> On Fri, Feb 7, 2014 at 8:41 PM, Joe Nosay > wrote: > >>> > >>> > >>> > >>> > >>> On Fri, Feb 7, 2014 at 4:15 AM, CeDeROM wrote: > >>>> > >>>> Lets make wiki page on freebsd website and start a repository with the > >>>> code and make it happen :-) > >>>> > >>>> Please let me know if/how I can help :-) > >>>> > >>>> -- > >>>> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info > >>> > >>> Okay, I need advice. I won't quit. Where and in what directory should I > >>> start. There is a build farm but it doesn't include FreeBSD. > >>> > >>> > >>> > >> > > > > > > What I have realized is that there needs to be an environment in which > > FreeBSD, Linux, and Google can share. > > My tutorial will be cleaned up. > > > > Here is what I have learned: > > 1. A Google FreeBSD environment can be created. > > 2. The filesystem must be ZFS. The architecture must be amd64/x86_64. The > > installations need to be CentOS and Debian on the FreeBSD Google > environment > > and the two Linux environments. > > 3. Emulation of the Linux systems will leave something to be desired. By > > comparing a build on a jailed Linux system to a bare metal Linux > install, > > we can see what needs to be done on FreeBSD. > > 4. The build environment allows the FreeBSD user to see how different > Linux > > distributions can be made to work together. E.g. What if the kernels > build > > faster in the Debian jail and the environments build faster in the CentOS > > jails? > > 5. Google and Linux developers will also have "native" environments while > > learning the layout and internals of FreeBSD. > > > > I had to realize that in order to deal with a Google project, one needs > to > > setup a Google environment. > > > > Okay, that is almost done. > > > > > Yes. That would be good. I need to setup blogger or what-have-you. Thanks for the idea.