[chromium-dev] Re: Problems compiling with xcode 3.1
I renamed tarball/ to tarball.old/ until someones creates new tarballs. On Tue, Jan 13, 2009 at 9:06 AM, Mike Pinkerton pinker...@chromium.org 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 kec...@gmail.com 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 j...@chromium.org 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 kec...@gmail.com 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 pinker...@google.com --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Problems compiling with xcode 3.1
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 mar...@chromium.orgwrote: I renamed tarball/ to tarball.old/ until someones creates new tarballs. On Tue, Jan 13, 2009 at 9:06 AM, Mike Pinkerton pinker...@chromium.org 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 kec...@gmail.com 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 j...@chromium.org 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 kec...@gmail.com 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 pinker...@google.com --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Problems compiling with xcode 3.1
Windows doesn't come with svn installed. Windows users want to download the depot_tools so they have svn. - Pam On Tue, Jan 13, 2009 at 12:14 PM, Marc-Antoine Ruel mar...@chromium.orgwrote: 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 p...@chromium.org 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 mar...@chromium.org wrote: I renamed tarball/ to tarball.old/ until someones creates new tarballs. On Tue, Jan 13, 2009 at 9:06 AM, Mike Pinkerton pinker...@chromium.org 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 kec...@gmail.com 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 j...@chromium.org 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 kec...@gmail.com 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 pinker...@google.com --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Problems compiling with xcode 3.1
The tarball is made with svn 1.4, so it should be OK. - Pam On Tue, Jan 13, 2009 at 1:09 PM, Mike Pinkerton pinker...@chromium.orgwrote: 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 mar...@chromium.org 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 p...@chromium.org 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 mar...@chromium.org wrote: I renamed tarball/ to tarball.old/ until someones creates new tarballs. On Tue, Jan 13, 2009 at 9:06 AM, Mike Pinkerton pinker...@chromium.org 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 kec...@gmail.com 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 j...@chromium.org 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 kec...@gmail.com 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 pinker...@google.com -- Mike Pinkerton Mac Weenie pinker...@google.com --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Problems compiling with xcode 3.1
OK, I see what you mean: the link now points to the base copy of depot_tools.zip. So no, I don't think we need these copies of depot_tools in archives/ anymore. But it's still better to rename the tgz file than the directory if you want to mark it as outdated; otherwise people's links break for less-obvious reasons. Hopefully none of this will matter soon, as the tarball will be updated more often. - Pam On Tue, Jan 13, 2009 at 1:21 PM, Pam Greene p...@chromium.org wrote: Windows doesn't come with svn installed. Windows users want to download the depot_tools so they have svn. - Pam On Tue, Jan 13, 2009 at 12:14 PM, Marc-Antoine Ruel mar...@chromium.orgwrote: 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 p...@chromium.org 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 mar...@chromium.org wrote: I renamed tarball/ to tarball.old/ until someones creates new tarballs. On Tue, Jan 13, 2009 at 9:06 AM, Mike Pinkerton pinker...@chromium.org 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 kec...@gmail.com 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 j...@chromium.org 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 kec...@gmail.com 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 pinker...@google.com --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Problems compiling with xcode 3.1
On Tue, Jan 13, 2009 at 4:28 PM, Pam Greene p...@chromium.org wrote: Hopefully none of this will matter soon, as the tarball will be updated more often. You made a cron job? --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Problems compiling with xcode 3.1
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 config http://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 kec...@gmail.com 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. --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Problems compiling with xcode 3.1
1) I installed xcode 3.1 in default location, /Developer/Applications. I am running leopard 10.5.6 2) Under Xcode's Project Set Active SDK, I have - Device - Iphone OS 2.0 - Device - Iphone OS 2.1 - Device - Iphone OS 2.2 - Simulator - same as above - Mac OS X 10.4 - Mac OS X 10.5 Note: the All project in Chrome was set to Use Project Settings, whose Base SDK is set to Current Mac OS 3) I don't remember if I have. Is there a quick way to verify? -Kelvin On Jan 12, 12:22 pm, Thomas Van Lenten thoma...@chromium.org wrote: Where did you install xcode? What os sdks did you install? Did you let it install the command line tools also? TVL On Mon, Jan 12, 2009 at 12:19 PM, kc kec...@gmail.com 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. --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Problems compiling with xcode 3.1
I actually did use gclient sync after untarring. but i will give your suggestion a try also. On Jan 12, 7:21 pm, Jon j...@chromium.org 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 kec...@gmail.com 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. --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
