On 9/19/08, Hector <[EMAIL PROTECTED]> wrote: > > Per Instructions: > > I have the commercial VS2005 with its SDK and with SP1 plus two Hot > Fixes. > > I installed Windows 2008 SDK as the Chrome Home Page says is > "supported" and you get compiling errors as I indicated. > > As did the PHP Windows Team "Worked very Hard" recompiling under the > VS200X environment they too finally, after a few pulled tooth, > realized they were not making it very easy to the interested parties > out there who wanted to rebuild PHP. They too have an mixed bag of > open source and dependency needs. I am seeing the same thing here. > > Don't get me wrong, I am trying to help and I will. > > You can't mix vs2005 with VISTA or 2008 (which the chrome home page > says is allowed) SDK. You might get it work with CHROME - but its a > mixed environment and prune to problems.
AFAIK this is not true. The SDK is not that much related to the version of visual studio. It is related to the target platform you want your application to run on. We have some vista specific stuff in our code, and we need to use the vista headers to use that. For example we use functions like SHOpenFolderAndSelectItems that are not defined in SDK before vista. We also need to work with Integrity Levels on Vista. All the defines related to that are not on the default SDK either. If you want your app to use new features of Vista, you need to use the Vista SDK. Nicolas > > I googled WINHTTP.H VS2005 and found this interesting link that I am > going to explore but I hate changing the code. > > > http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/8f29cb46-d89a-4c85-b056-ffdd653e5e1f/ > > And this is just VS, what about the non-VS stuff compiling error? Is > that SETUP related too? > > > 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 > > > Finally, please stop viewing this as layman issue. I'm a 30+ year vet > of the software industry with at least 100+ products under my belt in > 20+ different languages and multiple OSes, etc. I know what I am doing > and there are issues here. The last think I ever do is buck the > system and go against instructions. > > -- > > > > On Sep 19, 11:21 am, "Marc-Antoine Ruel" <[EMAIL PROTECTED]> wrote: > > I think the instructions are clear and they have been tested by > > non-developpers folk. Sorry to hear you have trouble with it. A fairly > > high number of external folks are already sending patches so I guess > > they are able to build the project. > > > > One thing to note, if you try to build the project and then in the > > interim, you install a new sdk, this is totally normal that you get > > link errors if you don't clobber your intermediary directories since > > the dependencies have changed. > > > > Please note that the Windows Server 2003 SDK is not supported, as > > > stated in the documentation located > > athttp://dev.chromium.org/developers/how-tos/getting-startedYou seem > > > quite confused about which SDK is supported by which compiler. Please > > > read thoroughly the Windows 2008 SDK release notes located > > athttp://msdn.microsoft.com/en-us/windowsserver/bb986638.aspx > > > > > Finally, I don't understand your frustrations; you tell us that > > Chromium has too many dependencies, then you say that Chromium is hard > > to build and is too slow to build, that's it? > > > > Thanks for your feedback, patches to improve the build speed or reduce > > the number of dependencies are usually welcome. Please follow the > > > instructions located > > athttp://dev.chromium.org/developers/contributing-codeto learn how to > > contribute patches. > > > > M-A > > > > 2008/9/19 Hector <[EMAIL PROTECTED]>: > > > > > > > > > > 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-1FC...";> > > > > > full download... > > >http://www.microsoft.com/downloads/details.aspx?familyid=EBA0128F-A77...";> > > > > > web install... > > >http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24..."; > > > > > > 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 -~----------~----~----~----~------~----~------~--~---
