From owner-freebsd-gecko@FreeBSD.ORG Tue Mar 11 01:03:02 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 E0E89619; Tue, 11 Mar 2014 01:03:01 +0000 (UTC) Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 89B8795A; Tue, 11 Mar 2014 01:03:01 +0000 (UTC) Received: by mail-ob0-f173.google.com with SMTP id gq1so7800466obb.32 for ; Mon, 10 Mar 2014 18:03:00 -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=OFmxv7XkoNFE7D/fjb67PAKWrIqcYgIgqYHTe4/viCE=; b=OAK8gNVY09R7PWLrHjVm8JJsSNganZOsXM1o46eftCW7/s1Np6Vrl4tZaaO73GzCGE u2RN7rFt7W6ByzVpXqD1FaRx1aD9Ai94ntv3HECApS/l8WBhxlEiNwqFOtEuMnAFBggf pZhlgiFTu4/AtLRHHnCszzTdS23L2OJJJzOpLrMjTbiR/uqhNHoLgMtIdYrYh6bY9LVr Fm9HAlrQhGK7mPSmTmSxy9jzwpDw9pQCjEIanUErIQDVWw1titObK9vJkDL/HXTMvd/E knnGifUHmWDnA2qMcJpUWEK7R6Xi5J7D0gvdD4Y0WRJ1t6KbUz8VXnHhZNiEOwmr0PV6 31RA== MIME-Version: 1.0 X-Received: by 10.182.247.68 with SMTP id yc4mr27243obc.67.1394499780775; Mon, 10 Mar 2014 18:03:00 -0700 (PDT) Received: by 10.182.76.201 with HTTP; Mon, 10 Mar 2014 18:03:00 -0700 (PDT) In-Reply-To: References: Date: Mon, 10 Mar 2014 21:03:00 -0400 Message-ID: Subject: Re: Making WebRTC available for FreeBSD From: Joe Nosay To: CeDeROM Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: chromium@freebsd.org, Adrian Chadd , Niklas Enbom , gecko@freebsd.org 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:03:02 -0000 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.