Chromium building error in Visual Studio 2008

[Yue Zhang]

Hi,

   I have tried to build the chromium using Visual Studio 2008 for the first time (after installing the depot_tools and getting the code). I got an error like:

   fatal error C1083: Cannot open include file:

   'policy/policy_constrants.h": No such file or directory

   I searched and found that somebody else have also met this problem (http://code.google.com/p/chromium/issues/detail?id=103701) but seems that no solution has been given yet.

   Anybody knows what could be the problem? Thanks very much!

Yue

[Greg Thompson]

Try building the cloud_policy_code_generate target (it generates the file policy_constants.h) and looking at the errors.

Yue

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

[Yue Zhang]

Thanks very much for your input.

I can successfully build "cloud_policy_code_generate" and now the previous error doesn't show up. So is it because visual studio didn't automatically build that target somehow?

And I'm now given another error:

Error result 1 returned from "c:\Program Files\Microsoft SDKs\Windows\v7.1\bin\rc.exe"

I couldn't find an answer for this error online, any ideas?

Thanks,

Yue

[Greg Thompson]

We'll need more context to figure that out.  What target was being built? Are there any other messages prior to that one?

[Yue Zhang]

It happened when I was trying to build "chrome" project. And this is the first and only error message shown.

Thanks,

Yue

[Greg Thompson]

On Tue, May 15, 2012 at 8:05 PM, Yue Zhang <zys...@google.com> wrote:

It happened when I was trying to build "chrome" project. And this is the first and only error message shown.

Try turning up the build logging verbosity.  The setting is under Tools -> Options -- Projects and Solutions -> Build and Run, or something like that.

[Yue Zhang]

Thanks. So now it shows some more detail:

"fatal error RC1110: could not open ..\build\Release\obj\global_intermediate\chrome_version\chrome_exe_version.rc"

I checked global_intermediate directory and there is no chrome_version directory under it. Any ideas?

Yue

[Greg Thompson]

I think there's a chrome_version_resources target that generates those .rc files. What happens if you build that target?

[Yue Zhang]

I found that those files is in my Debug directory but I was running a release version. So it could be that I changed the build configuration in the middle of the build process somehow...

From the previous email, I noticed that "cloud_policy_code_generate" project need to be built when building "chrome" project. Does it means every time (or at least the first time) I need to build the entire solution rather than just the "chrome" project? I'm now building the entire solution and it works OK. I'm not very familiar with the relationship between "solution" and "project" in VS. But intuitively we should be able to build just "chrome" project, right?

Thanks,

Yue 

[Gabriel Charette]

(and actually replying-all this time!)

On Thu, May 17, 2012 at 2:44 PM, Yue Zhang <zys...@google.com> wrote:

I found that those files is in my Debug directory but I was running a release version. So it could be that I changed the build configuration in the middle of the build process somehow...

From the previous email, I noticed that "cloud_policy_code_generate" project need to be built when building "chrome" project. Does it means every time (or at least the first time) I need to build the entire solution rather than just the "chrome" project? I'm now building the entire solution and it works OK. I'm not very familiar with the relationship between "solution" and "project" in VS. But intuitively we should be able to build just "chrome" project, right?

RIght, but you need to build the "chrome" project while browsing the "chrome.sln" solution in VS (or all.sln, mini_installer.sln, etc.) as the solution is what nows the dependencies on other projects IIRC.

Cheers,

Gab

[Yue Zhang]

hm... I think I did build "chrome" project in the "chrome.sln" solution (by double-clicking chrome.sln) when that dependency problem occurs.

Actually I'm not sure I build the "right" chrome project. My goal is to build a chrome.exe without running those tests. So I build the following project in the solution explorer:

Solution 'chrome' (538 projects)

...

chrome

   ...

   chrome  <----- I built this one by right clicking it and select project only->build only chrome.

   ...

...

Looks like this chrome project cannot build a chrome.exe. Did I choose the wrong project?\

Thanks,

Yue

[Scott Graham]

If you only build that project, not surprisingly, it only builds that
project and not its dependencies.

You just want Build, not Project Only -> Build.

[Brett Wilson]

On Fri, May 18, 2012 at 11:47 AM, Yue Zhang <zys...@google.com> wrote:

> hm... I think I did build "chrome" project in the "chrome.sln" solution (by
> double-clicking chrome.sln) when that dependency problem occurs.
>
> Actually I'm not sure I build the "right" chrome project. My goal is to
> build a chrome.exe without running those tests. So I build the following
> project in the solution explorer:

"build only" builds just that project and not its dependencies. You
need to do "build".

Brett

[Yue Zhang]

Oh, that explains! Thanks all!

Yue