From owner-freebsd-gecko@FreeBSD.ORG Tue Mar 11 01:04:05 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 AEC8563A; Tue, 11 Mar 2014 01:04:05 +0000 (UTC) Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5761E95F; Tue, 11 Mar 2014 01:04:05 +0000 (UTC) Received: by mail-qc0-f174.google.com with SMTP id x13so8499933qcv.5 for ; Mon, 10 Mar 2014 18:04:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Sf18mojP2cZgsV1wK9RhQAXM7nJZ/nrrnM0S90lWuSk=; b=Dfpxo/zVfD8G4KDUSVxiLrCX8jjtK2ON/KrmUVBw7psv9LeX14DisFfcRpeZ796eXa ZBAwzPg+Bqya8ewLzwlwo9hfjZtFs3B/Kc3a2IMd9b4G7AMRrrAW5dTub8AR+3llPeM2 KGgYHmHDuyoEtgbx4AnSSv6NibfJKEp85KGh6fa7V6fFVt9Z6yURShFsIbrqD3+2WkxK MNTUkyD282t7aBWFR90GkRo9GqgZAOPPmGGk5GoTf80oEeKdldEw230E/wpojRdlQQUH R9Pwti4m+4oNp6gLZG7XLbHWauBOnYDKodA4/sH15/Uw6mi7ToO6UCOH2W68Nw16k/bl +N+Q== MIME-Version: 1.0 X-Received: by 10.224.104.1 with SMTP id m1mr15484325qao.51.1394499844337; Mon, 10 Mar 2014 18:04:04 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.8.137 with HTTP; Mon, 10 Mar 2014 18:04:04 -0700 (PDT) In-Reply-To: References: Date: Mon, 10 Mar 2014 18:04:04 -0700 X-Google-Sender-Auth: z7suih2OQL2zG_a4EAOz7VEf2tE Message-ID: Subject: Re: Making WebRTC available for FreeBSD From: Adrian Chadd To: Joe Nosay Content-Type: text/plain; charset=ISO-8859-1 Cc: chromium@freebsd.org, gecko@freebsd.org, Niklas Enbom , CeDeROM 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: Tue, 11 Mar 2014 01:04:05 -0000 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. > >