Also, the default svn on Mac is 1.4. If someone on windows/linux pulls a tree with 1.5, will that affect the ability of the tarball to update?
On Tue, Jan 13, 2009 at 3:14 PM, Marc-Antoine Ruel <[email protected]> wrote: > > Yes but I fixed the wiki link to directly pull from svn. I don't see > any reason to keep at copy of depot_tools at that place ? > > On Tue, Jan 13, 2009 at 2:31 PM, Pam Greene <[email protected]> wrote: >> That broke archives/, which is a link to tarball/ but also contains the >> depot_tools. I renamed tarball.old/ back to tarball/ and renamed >> chromium.tgz to chromium.old.tgz instead. Also I'll upload a new tarball >> today. >> - Pam >> >> On Tue, Jan 13, 2009 at 6:21 AM, Marc-Antoine Ruel <[email protected]> >> wrote: >>> >>> I renamed tarball/ to tarball.old/ until someones creates new tarballs. >>> >>> On Tue, Jan 13, 2009 at 9:06 AM, Mike Pinkerton <[email protected]> >>> wrote: >>> > >>> > Hrm, I'm not sure anyone has tried the tarball in a while. I think the >>> > last person who did said it didn't work. What about if you pull from >>> > scratch from svn? Does it still happen? >>> > >>> > On Mon, Jan 12, 2009 at 7:40 PM, kc <[email protected]> wrote: >>> >> >>> >> I actually did use gclient sync after untarring. >>> >> but i will give your suggestion a try also. >>> >> >>> >> On Jan 12, 7:21 pm, Jon <[email protected]> wrote: >>> >>> You probably used svn directly instead of >>> >>> gclient.http://dev.chromium.org/developers/how-tos/get-the-code >>> >>> >>> >>> I think you can recover by going into your repository directory (not >>> >>> into >>> >>> src) and using: >>> >>> >>> >>> gclient confighttp://src.chromium.org/svn/trunk/src >>> >>> >>> >>> Then use: >>> >>> >>> >>> gclient sync >>> >>> >>> >>> Then always use gclient sync instead of svn sync. >>> >>> >>> >>> Jon >>> >>> >>> >>> On Mon, Jan 12, 2009 at 9:19 AM, kc <[email protected]> wrote: >>> >>> >>> >>> > Hi, >>> >>> > I am kind of new to this. Could someone pls kindly help & provide >>> >>> > me >>> >>> > with some guidance? >>> >>> >>> >>> > I ran into tons and tons of compilation errors with xcode 3.1. (I >>> >>> > downloaded the tarball base >>> >>> > and did a sync while tree is opened). The first error I ran into >>> >>> > said >>> >>> > it couldnt find the header file >>> >>> > "carbon/carbon.h" in an include of one of the cc files. What I >>> >>> > noticed >>> >>> > is that "Carbon/Carbon.h" (Upper Case) >>> >>> > will rid of that particular error. Lot of errors look like it doesnt >>> >>> > know how to handle header files. >>> >>> > I speculate one can fix this in the Build Settings (under Project > >>> >>> > Edit Project Settings). >>> >>> > I went there and under the Build tab, I am wondering why it only >>> >>> > contained user defined settings, >>> >>> > and missing all the others (eg. "Compiler Version", "Search Paths"). >>> >>> >>> >>> > Thanks. >>> >> > >>> >> >>> > >>> > >>> > >>> > -- >>> > Mike Pinkerton >>> > Mac Weenie >>> > [email protected] >>> > >>> > > >>> > >>> >>> >> >> >> > >> > > > > -- Mike Pinkerton Mac Weenie [email protected] --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
