chrome.xcodeproj cannot be opened because it is missing its project.pbxproj file.

[muhammad haris]

I want to debug chromium in xcode using hybrid approach as explained here. To do this I performed following steps:

1. on terminal, inside chromium/src folder run: set GYP_GENERATORS=ninja,xcode-ninja
2. on terminal, inside chromium/src folder run: set GYP_GENERATOR_FLAGS= xcode_ninja_main_gyp=src/build/ninja/all.ninja.gyp
3. on terminal, inside chromium/src folder run:gclient runhooks
4. According to official document, I should open src/build/ninja/all.ninja.xcworkspace

However I am not able to found such folder in my source code. Also, in building with ninja debugging with xcode tutorial from chromium it is mentioned to open chrome.xcodeproj, that I found in src/chrome folder. However it gives me following error.

chrome.xcodeproj cannot be opened because it is missing its project.pbxproj file.

[Sylvain Defresne]

In steps 1. and 2., you need to use "export" to make the values visible to gyp, i.e. you're supposed to run the following commands:

cd chromium/src

export GYP_GENERATORS=ninja,xcode-ninja

export GYP_GENERATOR_FLAGS=xcode_ninja_main_gyp=src/build/ninja/all.ninja.gyp

gclient runhooks

open build/ninja/all.ninja.xcworkspace

Does this help?

-- Sylvain

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

[muhammad haris]

Hi Thanks, it works like charm. I am not sure why official documentation can not include these steps. One more thing can you please tell me does it take hours to load all.ninja.xcworkspace in xcode? 

[Sylvain Defresne]

If you want to fix the documentation, you're welcome to contribute a patch to improve it.

Since you have already checked out a Chromium tree, the file should be accessible as chromium/src/docs/mac_build_instructions.md.

Regarding opening the project itself, it is pretty fast on my machine, but I have a fully beefed up Mac Pro (12 cores, 64 GB of RAM, fast 1TB SSD) so I may not be the most representative.

-- Sylvain

[Torne (Richard Coles)]

The documentation assumes you know how environment variables work and that you have to export them for other programs to be able to see them. This could be fixed to be more explicit and not require people already know this.