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
