Build.ninja created

[Joe Nosay]

Where do I place the file? I'll probably get this right on my own.

What I did was build from the original ninja github.

[Nico Weber]

What?

On Tue, Feb 18, 2014 at 4:51 PM, Joe Nosay <superb...@gmail.com> wrote:

Where do I place the file? I'll probably get this right on my own.

What I did was build from the original ninja github.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Daniel Bratell]

On Wed, 19 Feb 2014 01:51:22 +0100, Joe Nosay <superb...@gmail.com>
wrote:

> Where do I place the file? I'll probably get this right on my own.What I

> did was build from the original ninja github.

In chromium build.ninja is generated by gyp which is run among other
things from gclient runhooks.

Or you can run build/gyp_chromium and if you have all the source code, you
will get a build.ninja in out/Debug and one in out/Release.

But most likely you should just use the build instructions. Try
http://code.google.com/p/chromium/wiki/NinjaBuild

/Daniel

[Joe Nosay]

On Wed, Feb 19, 2014 at 4:58 AM, Daniel Bratell <bra...@opera.com> wrote:

On Wed, 19 Feb 2014 01:51:22 +0100, Joe Nosay <superb...@gmail.com> wrote:

Where do I place the file? I'll probably get this right on my own.What I did was build from the original ninja github.

In chromium build.ninja is generated by gyp which is run among other things from gclient runhooks.

Or you can run build/gyp_chromium and if you have all the source code, you will get a build.ninja in out/Debug and one in out/Release.

What I did was git the original ninja program, build it, and then port the entire ninja directory to the chromium base/ directory and rebuild ninja. The output is still for Linux- I'll need to change that environmental variable soon- ;however, it, being build.ninja, is being built on FreeBSD and that is good.

[Nico Weber]

On Wed, Feb 19, 2014 at 4:21 PM, Joe Nosay <superb...@gmail.com> wrote:

On Wed, Feb 19, 2014 at 4:58 AM, Daniel Bratell <bra...@opera.com> wrote:

On Wed, 19 Feb 2014 01:51:22 +0100, Joe Nosay <superb...@gmail.com> wrote:

Where do I place the file? I'll probably get this right on my own.What I did was build from the original ninja github.

In chromium build.ninja is generated by gyp which is run among other things from gclient runhooks.

Or you can run build/gyp_chromium and if you have all the source code, you will get a build.ninja in out/Debug and one in out/Release.

What I did was git the original ninja program, build it, and then port the entire ninja directory to the chromium base/ directory and rebuild ninja. The output is still for Linux- I'll need to change that environmental variable soon- ;however, it, being build.ninja, is being built on FreeBSD and that is good.

(I think you can install ninja on FreeBSD by running `pkg install ninja` too.)

 

But most likely you should just use the build instructions. Try http://code.google.com/p/chromium/wiki/NinjaBuild

/Daniel

[Thiago Farina]

On Wed, Feb 19, 2014 at 9:21 PM, Joe Nosay <superb...@gmail.com> wrote:

On Wed, Feb 19, 2014 at 4:58 AM, Daniel Bratell <bra...@opera.com> wrote:

On Wed, 19 Feb 2014 01:51:22 +0100, Joe Nosay <superb...@gmail.com> wrote:

Where do I place the file? I'll probably get this right on my own.What I did was build from the original ninja github.

In chromium build.ninja is generated by gyp which is run among other things from gclient runhooks.

Or you can run build/gyp_chromium and if you have all the source code, you will get a build.ninja in out/Debug and one in out/Release.

What I did was git the original ninja program, build it, and then port the entire ninja directory to the chromium base/ directory

by "port the entire ninja directory to the chromium base/ directory", what you mean exactly? Do you mean you changed ninja code to reuse base APIs? Was that?

Sorry, I'm having trouble trying to figure out what you want from us, and how that is relevant for Chromium browser. Are you trying to port ninja to FreeBSD? 

Please, be more clear about what you are doing and how can we help you if it is related to Chromium.

--

Thiago Farina

[Joe Nosay]

Yes. I am porting ninja, chromium, webrtc, depot_tools, chromium/src, and chromium/base to work natively on FreeBSD.

http://forums.freebsd.org/viewtopic.php?f=39&t=44691 shows my progress.

The process is being made into a tutorial for the following reasons.

1. All changes are made public and do not break any license.

2. Readers/viewers see what needs to be done and can be part of the build/porting process.

3. Because it is being done on FreeBSD, the forums are the most neutral area to follow.

Putting it all into perspective::

Having a stand alone and native version of WebRTC on FreeBSD means following the path that was used to build Chromium, libjingle, and WebRTC then recreating the environment.

I am doing that right now.

Every Linux or MacOSX reference that can be found with basic grep and locate commands on FreeBSD are being used to replace and recreate where the text exists or needs to exist in a file. The file is being saved under a new name,

For those processes which do not have an exact FreeBSD equivalent,  similar process that does the same function is referenced towards in all edited/changed code.

Clang output errors are used to edit the syntax of any given file on the system.

The porting of brltty is on hold while the WebRTC portions are being built/edited. This is a FreeBSD and Clang specific set of problems.

The reason for jumping around is that those items are what I perceive at that moment to be "fixable" by me.

[Joe Nosay]

So I am basically porting the entire chromium directory and depends to FreeBSD to make the effort work.

[Thiago Farina]

On Wed, Feb 19, 2014 at 11:28 PM, Joe Nosay <superb...@gmail.com> wrote:

So I am basically porting the entire chromium directory and depends to FreeBSD to make the effort work.

Good luck!

--

Thiago Farina