PlatformSDK\include

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Rajko

    #1

    PlatformSDK\include

    PlatformSDK\inc lude vs include
    Why ??
    Why they made two different versions of the same header files.
    for example comdef.h is shortened in include(no interface GUID definition)
    while in PlatformSDK\inc lude it's full version ?? WHY ??

    Can someone please tell me?
    Thanks.

    BTW is it ok to put PlatformSDK\inc lude before include ?




  • Carl Daniel [VC++ MVP]

    #2
    Re: PlatformSDK\inc lude

    Rajko wrote:[color=blue]
    > PlatformSDK\inc lude vs include
    > Why ??
    > Why they made two different versions of the same header files.
    > for example comdef.h is shortened in include(no interface GUID
    > definition) while in PlatformSDK\inc lude it's full version ?? WHY ??
    >
    > Can someone please tell me?[/color]

    The headers, libraries, etc, within the PlatformSDK folder "belong to" to OS
    group, who produces the platform SDK. The headers in the Include directory
    "belong to" the VC team, who produces the compiler. Splitting them into two
    directories makes it much easier to update the PlatformSDK, which is
    released about 4 times as frequently as new compiler versions are.
    [color=blue]
    > Thanks.
    >
    > BTW is it ok to put PlatformSDK\inc lude before include ?[/color]

    That is normally the appropriate order in which to put them. I don't know
    why the default order has PlatformSDK coming after the VC include
    directories.

    -cd


    Comment

    Working...