The way it is stated in the Chrome Windows Build home page, it is
promoting Mixed and Confused compiling environments.
Even if you are able to get past the compiler, the linking
may be a problem, and
even if you get past the linking, you are not 100% sure
that you will have a
stable EXE image with proper expectations of DLLS and
libraries.
If the Chrome Build Requirements allows for:
VS 2005
VS 2008
Then for VS2005, the build instructions can not tell people to install
2008/VISTA SDK because now you have a mixed bag. (I can see Microsoft
didn't help either by trying to blend it in - 80%, not 100%).
The proper SDK for VS2005 is:
Windows Server 2003 SP1 Platform SDK - April 2005 Edition
ISO install...
http://www.microsoft.com/downloads/details.aspx?familyid=D8EECD75-1FC4-49E5-BC66-9DA2B03D9B92";>
full download...
http://www.microsoft.com/downloads/details.aspx?familyid=EBA0128F-A770-45F1-86F3-7AB010B398A3";>
web install...
http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5";
But I don't know if this is going to solve the few dependencies some
developers used the 2008/VISTA SDK for. Off hand, what I had initial
trouble with was:
COPY_FILE_COPY_SYMLINK
Used for CopyFileEx()
PSAPI_WORKING_SET_INFORMATION
PSAPI_WORKING_SET_BLOCK
Used for QueryWorkingSet()
If this is the only thing CHROME needs the 2008/VISTA SDK for, it is
totally unnecessary.
In the end, if people are using VS2005, they really should not use the
2008/VISTA SDK. This will promote problems.
Personally, I don't see why Chrome is so depended on VS2008 stuff. It
why it can't even be compiled under VS6.0 with the final FEB 2003 SDK.
==
On Sep 19, 9:23 am, Hector <[EMAIL PROTECTED]> wrote:
> Folks,
>
> I'm seeing the same dumb issues with Chrome that I saw with the PHP
> Windows Team - a complete mess when it came to the idea of rebuilding
> an exact image as the Chrome Team put it out. They went thru a
> complete mess and headache of finally getting it straight with me
> helping it push it.
>
> It all starts with the idea the Microsoft is throwing out these free C/
> C++ compilers and SDK and they are a mix bag of them, and unix
> people, doing things for Windows, begin to use these free compilers
> and SDK, well, it doesn't match very well with established windows
> developers.
>
> Case in point, we are a established VS 6.0 company and product
> manufacturing company. We have VS2005 and have been moving towards
> it. Keeping the includes and libraries separate are important for
> product completeness, stability and reliability.
>
> Under normal circumstances we would not INSTALL the Windows 2008/VISTA
> SDK simply because we don't have the VS2008 compiler.
>
> From my 2 days exploration of trying to build chrome I see it has a
> few dependencies on ATL, WinHTTP and MFC. Well, these don't come with
> the free VS2005 and VS2008.nor the FREE SDK. You need the commercial
> versions.
>
> So here is is what happens.
>
> Thinking I can compile Chrome with my commercial VS2005 Professional
> package, the Chrome team, and I think it was innocently done
> unbeknowst to them, created a dependency on the commercial VS2008 and
> the 2008/VISTA SDK.
>
> So installing the 2008/VISTA SDK on top of my VS2008, I see C/C++
> environment compiling problems like so:
>
> 3>F:\Program Files\Microsoft SDKs\Windows\v6.1\Include
> \winhttp.h(399) : error C2061: syntax error : identifier
> '__out_data_source'
> ..
>
> F:\Program Files\Microsoft SDKs\Windows\v6.1\Include\ws2ipdef.h(157) :
> error C2146: syntax error : missing ';' before identifier
> 'sin6_family'
>
> and so on, there are other non SDK related compiler errors like so:
>
> g:\files\browsers\chrome\trunk\src\third_party\webkit\webcore\svg
> \SVGElement.h(32) : fatal error C1083: Cannot open include file:
> 'SVGNames.h': No such file or directory
>
> but overall, what needs to get done here is a clear concise
> documentation of the following:
>
> 1) For the builds, a log of the snapshot of the exact building
> environment is required, listing all the include and lib statements.
>
> 2) A better explanation of the building requirements and not throw it
> out there with a mix bag of compilers and sdk.
>
> One of the headers, I believe it was win_util.h and maybe another
> header, had inline author comments that said 2008/VISTA SDK is
> required and the Chrome Windows Build home page says that this is ok
> with VS2005.
>
> Well, its not.
>
> Overall, I saw things that didn't require the 2008/VISTA SDK headers.
> I saw two things, but there could of been more, that easily could be
> replace with 100% WIN32 compatible functionality.
>
> I just hope this can get straight. Spending far too much time trying
> to get this thing build.
>
> --
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
