Hi Matt, Actually eventually that will probably be the case, but for the time being, we're sticking with separate trees. We were on a course for merging the two trees, but decided to put that off a bit while we work on other things.
So, if you're going to build O3D, you will need a separate tree, because the Chrome DEPS file is missing some of the things that O3D needs to build (nixysa and the vectormath library, and a few other things). -Greg. On Mon, Nov 16, 2009 at 9:06 AM, Matt Richards <[email protected]> wrote: > I orginally posted this on the o3d discussion list, however it does > not appear to be the correct place. > I will try on this list. > > > ---------- Forwarded message ---------- > From: Matt Richards <[email protected]> > Date: Fri, Nov 13, 2009 at 9:26 PM > Subject: O3D and Chromium Source Trees > To: O3D-discuss <[email protected]> > > > I've noticed the build system for O3D has been migrated over to GYP > now, and I see more code being contributed to the chromium project as > a whole. > I have the source tree for chrome sitting here taking up a lot of disk > space, a long side with the O3D project both from the same repository, > just slightly different paths. I've noticed they share a lot of > similar DEPS and such. Do I still need to maintain a secondary source > tree to build O3D? > > I'm assuming at some point this will not be needed and everything will > be migrated into the chromium project as a whole.. Am I on the right > thoughts here? > > > > -- > --Matt > > -- > Chromium Discussion mailing list: [email protected] > View archives, change email options, or unsubscribe: > http://groups.google.com/group/chromium-discuss > -- Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss
