Nicolas Sylvain wrote:
> On 9/19/08, Hector <[EMAIL PROTECTED]> wrote:

> >  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.

I disagree.  Again, very simple:  a pure VS2005 (commercial) with all
the service packs + hotfixs, addng the current rendition of the 2008/
VISTA SDK will give you problems.

Now if they are other "after the fact" gotchas, thats a different
story, but when I see, there are 2008/VISTA SDK dependencies and from
what I can see, for concepts that are most definitely doable with such
a  dependency.

> We have some vista specific stuff in our code, and we need to use the
> vista headers to use that.

Like what?  I only see two things and its definitely WIN32 compatible
with the 2008/VISTA SDK.  It just to use a easy syntax made possible
under this newer SDK but totally unnecessary.

> 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.

Concepts that are doable without VISTA headers. Obviously, because the
same functionality applies for other OSes before VISTA.  You (speaking
in general) choose to use something that wasn't required.

> If you want your app to use new features of Vista, you need to use the
> Vista SDK.

So you made a decision that CHROME is for VISTA only?

 I am not out to make false statements - only what is experienced and
what I see in front in me.  This is all deja-vu as with the PHP people
who "thought" they had it all correct with VS 200X building and in the
end it was not when I came into the scene..  It the same thing here.

What you are failing to understand that development is not isolated to
CHROME only and people need to have the proper enviromment across the
board.    You guys well, how should I saw it politely?  KLUDGING a
compile!

In any case, what about this error?

  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

Is this also related to the VS vs SDK situation?

Thanks


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to