Native build of chromium/webrtc source requires full path in /usr/local

[Joe Nosay]

On Tue, Mar 4, 2014 at 2:23 PM, Raphael Kubo da Costa <rakuco at freebsd.org>wrote:

> Joe Nosay <superbisquit at gmail.com> 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 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-chromium
> To unsubscribe, send any mail to "freebsd-chromium-unsubscribe at 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.