I'm going to see if I can fnd my PHP windows build notes, I had produced a neat table based on what compiler you had, the minimum SDK or PSDK required that properly match the includes and libraries. Hopefully I can find it quickly and don't need to reproduce it again.
-- 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 -~----------~----~----~----~------~----~------~--~---
