From owner-freebsd-chromium@FreeBSD.ORG Wed Mar 5 00:49:32 2014 Return-Path: Delivered-To: freebsd-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 DDC12A41; Wed, 5 Mar 2014 00:49:32 +0000 (UTC) Received: from mail-qa0-x22e.google.com (mail-qa0-x22e.google.com [IPv6:2607:f8b0:400d:c00::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8916B35F; Wed, 5 Mar 2014 00:49:32 +0000 (UTC) Received: by mail-qa0-f46.google.com with SMTP id i13so330893qae.5 for ; Tue, 04 Mar 2014 16:49:31 -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=l3xEfdDrwUbxFMl5BYAjK2I1Lw39/pUmbNEKXStO4us=; b=OZYVfSxhUy1ZAr/ZlCnTaJzfF92k96NXcuRI6mI8ItFPL3TgS42t9fEyA69By1LOUy 1vv8Auxfl6rge4j91oqIQ2pDBZdrnK2z2/IQ/2XjpbarhZhNdU1BL5XhjIo4b1RPDJQf c4Q4kC1SxGxTQ/0ecyl7nf0J17+nwlZMAY2OD8kwTvTPRY3ESXPqmG9AosniWtAMqy1o v3g70Zm/NRx59fyhisorL1Js6zzQsydYhYOPjDVfrgk6mmLWtQVqwsXKFmi8MbK+gG09 RPjKJxOtilZ7o0htJ+tHM2ZW5Vw3HdDxXGsLdMS9fxa1x/p2tigjciRVCK3hKQbz7VU3 MkWQ== MIME-Version: 1.0 X-Received: by 10.140.85.35 with SMTP id m32mr3282190qgd.40.1393980571584; Tue, 04 Mar 2014 16:49:31 -0800 (PST) Received: by 10.96.144.101 with HTTP; Tue, 4 Mar 2014 16:49:31 -0800 (PST) In-Reply-To: <867g89n4y3.fsf@orwell.Elisa> References: <867g89n4y3.fsf@orwell.Elisa> Date: Tue, 4 Mar 2014 19:49:31 -0500 Message-ID: Subject: Re: Native build of chromium/webrtc source requires full path in /usr/local From: Joe Nosay To: Raphael Kubo da Costa Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-chromium@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 Mar 2014 00:49:32 -0000 On Tue, Mar 4, 2014 at 2:23 PM, Raphael Kubo da Costa wrote: > Joe Nosay writes: > > > I've had to rewrite the paths on h, c, and cc files for the build to > > continue. The assumption, and hopefully not a faulty one, is that the > port > > Makefile can be edited so that any build from the Google Chrome Framework > > can be ported to FreeBSD. Fewer files than thought of need to be changed; > > and, even on the ChromeOS build, I have noticed that vfs.h references can > > be replaced with NFS references- it's basically the same thing, which may > > be good if someone is interested in having a ChromeOS Linux compatibility > > layer. > > > > Will the assumption work; and, if so, then what parts will I need to work > > on? > > I couldn't really understand your question. Can you post an example of a > change you had to make? > > _______________________________________________ > freebsd-chromium@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium > To unsubscribe, send any mail to "freebsd-chromium-unsubscribe@freebsd.org > " > The project- which has become replicating the environment to run on FreeBSD- is being moved into a jail. I am not sure as to the method that Google uses to search for the libraries, binaries, and such. What I can do is use the full path - /$SYSROOT/$USR_PATH/$FILE- to let the c and h files find what is needed. ChromiumOS, Chromium Browser, and Android (environment and SDK) can be ported and worked from the FreeBSD system. Input data locations need to be modified as well as the build to use CLang in place of GCC. This will be the FreeBSD developers' environment that Google did not set up.