compilation error: ConvertStringSecurityDescriptorToSecurityDescriptor

I am comliling user-mode dll from DDK build window (DDK version 3790).
After I added security attributes code, I get compilation errors.

I tried to include "sddl.h" file. I even tried to give include path
for sddl.h.
But still "Cannot open file sddl.h". I dont see sddl.h anywhere in
c:\winddk. I found few DACL related definitions in wdm.h which is
included in my workspace.

How can I compile code with function
"ConvertsecurityDescriptorToSecurityDescriptor" from DDK window.


TARGETTYPE=DYNLINK
DLLENTRY=DLLMain

TARGETLIBS=$(SDK_LIB_PATH)\kernel32.lib \
$(SDK_LIB_PATH)\user32.lib \
$(SDK_LIB_PATH)\setupapi.lib \
$(SDK_LIB_PATH)\winmm.lib \
$(SDK_LIB_PATH)\advapi32.lib


USE_MAPSYM=1
USE_MSVCRT=1
DEBUG_CRTS=1
UMTYPE=windows

USER_C_FLAGS=/FAcs

SYNCHRONIZE_BLOCK=1

INCLUDES=..\..\inc; \
..\..\driver\common; \
c:\winddk\inc\wnet; \
c:\Program Files\Microsoft Platform SDK\Include; \
C:\Program Files\Microsoft SDK\Include

SOURCES= 1394apidll.c \
1394dllmain.c

Eliyas
Tue Nov 18 10:56:45 CST 2003

There is a typo in your function name.

Try ConvertSecurityDescriptorToStringSecurityDescriptor.

From MSDN:

Header: Declared in Sddl.h.
Library: Use Advapi32.lib.

--
-Eliyas
This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.microsoft.com/whdc/hwdev/driver/kb-drv.mspx

r_konjeti
Tue Nov 18 20:04:50 CST 2003

> There is a typo in your function name.

Sorry, typing error was only in posting. My code is using correct
function name: ConvertStringSecurityDescriptorToSecurityDescriptor.

It is some configuration issue bugging me, not spelling error.

I included Sddl.h path in include path of sources, but compiler error
says "Cannot open Sddl.h". I am compiling fromn DDK window.

Kirk
Wed Nov 19 02:57:02 CST 2003

"Raj" <r_konjeti@mailcity.com> wrote in message
news:8509fde8.0311181804.74685322@posting.google.com...
> It is some configuration issue bugging me, not spelling error.
>
> I included Sddl.h path in include path of sources, but compiler error
> says "Cannot open Sddl.h". I am compiling fromn DDK window.

The file is only available when you build in the Windows Server 2003
environment (simply because the SDK_INC_PATH gets updated appropriately)

-Kirk

Eliyas
Wed Nov 19 09:06:06 CST 2003

Yep, there is no typo in the function name given in the subject line. I
should have seen that. Anyways, as Kirk pointed out that this file is there
only in Server 2003 inc path. This should be available for all three build
environments. For the time being if you want to use this file for other
(Win2K or XP) build environments, just copy it over. I didn't see any major
changes to this file since Win2K SP3. I hope there is no other dependency. I
will file a bug report to get this file included for other build
environments.


--
-Eliyas
This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.microsoft.com/whdc/hwdev/driver/kb-drv.mspx

r_konjeti
Wed Nov 19 16:53:41 CST 2003

>>Anyways, as Kirk pointed out that this file is there
>>only in Server 2003 inc path. This should be available for all three
build
>>environments.

Thank you Eliyas and Kirk. I am able to compile the "createDACL" code
from Win2k DDK window after copying Sddl.h into my workspace
directory.

What I still dont understand is why compiler is ignoring the include
path specified for Sddl.h. Whereever the file is, compiler should find
the header file, if the file path is given in sources file INCLUDES?

Thank you very much.