Hi,

I'm using the winddk (6000) to not only develop a WDF driver, but also a
console app that tests out my driver (using IOCTLs). When I include
<iostream> in the console app, the ddk compiler can't find it. I did find it
in c:\winddk\6000\inc\api\crt\stl70. The test app uses classes and "new"
constructs, but I can't seem to include <iostream> for stl::cout and the
like.

Here is my sources file for the app
==============================================================
TARGETNAME=rmgr
TARGETTYPE=PROGRAM

UMTYPE=console
UMENTRY=main

USE_MSVCRT=1

!if defined(DDKBUILDENV)
C_DEFINES = $(C_DEFINES) -DDDKBUILD=1
!endif

TARGETLIBS=$(SDK_LIB_PATH)\setupapi.lib \
$(SDK_LIB_PATH)\user32.lib \


INCLUDES=$(INCLUDES);$(DDK_INC_PATH);

SOURCES= \
rmgr.cpp

RUN_WPP= $(SOURCES) #-func:printf(MSG,...)

=========================================================

thanks in advance for help,
cm

Re: iostream by Carey

Carey
Thu Dec 21 11:38:42 CST 2006

Forgot to mention... I did include the stl70 path in the sources file on the
INCLUDES line, but that only caused more errors

cm


"Carey McMaster" <mcmaster@stargen.com> wrote in message
news:uI2nMZSJHHA.4384@TK2MSFTNGP03.phx.gbl...
> Hi,
>
> I'm using the winddk (6000) to not only develop a WDF driver, but also a
> console app that tests out my driver (using IOCTLs). When I include
> <iostream> in the console app, the ddk compiler can't find it. I did find
> it in c:\winddk\6000\inc\api\crt\stl70. The test app uses classes and
> "new" constructs, but I can't seem to include <iostream> for stl::cout and
> the like.
>
> Here is my sources file for the app
> ==============================================================
> TARGETNAME=rmgr
> TARGETTYPE=PROGRAM
>
> UMTYPE=console
> UMENTRY=main
>
> USE_MSVCRT=1
>
> !if defined(DDKBUILDENV)
> C_DEFINES = $(C_DEFINES) -DDDKBUILD=1
> !endif
>
> TARGETLIBS=$(SDK_LIB_PATH)\setupapi.lib \
> $(SDK_LIB_PATH)\user32.lib \
>
>
> INCLUDES=$(INCLUDES);$(DDK_INC_PATH);
>
> SOURCES= \
> rmgr.cpp
>
> RUN_WPP= $(SOURCES) #-func:printf(MSG,...)
>
> =========================================================
>
> thanks in advance for help,
> cm
>



Re: iostream by Maxim

Maxim
Thu Dec 21 11:42:56 CST 2006

Use stdio.h instead.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

"Carey McMaster" <mcmaster@stargen.com> wrote in message
news:uI2nMZSJHHA.4384@TK2MSFTNGP03.phx.gbl...
> Hi,
>
> I'm using the winddk (6000) to not only develop a WDF driver, but also a
> console app that tests out my driver (using IOCTLs). When I include
> <iostream> in the console app, the ddk compiler can't find it. I did find it
> in c:\winddk\6000\inc\api\crt\stl70. The test app uses classes and "new"
> constructs, but I can't seem to include <iostream> for stl::cout and the
> like.
>
> Here is my sources file for the app
> ==============================================================
> TARGETNAME=rmgr
> TARGETTYPE=PROGRAM
>
> UMTYPE=console
> UMENTRY=main
>
> USE_MSVCRT=1
>
> !if defined(DDKBUILDENV)
> C_DEFINES = $(C_DEFINES) -DDDKBUILD=1
> !endif
>
> TARGETLIBS=$(SDK_LIB_PATH)\setupapi.lib \
> $(SDK_LIB_PATH)\user32.lib \
>
>
> INCLUDES=$(INCLUDES);$(DDK_INC_PATH);
>
> SOURCES= \
> rmgr.cpp
>
> RUN_WPP= $(SOURCES) #-func:printf(MSG,...)
>
> =========================================================
>
> thanks in advance for help,
> cm
>
>


Re: iostream by Carey

Carey
Thu Dec 21 11:59:35 CST 2006

stdio.h doesn't know anything about stl::cout? How does your suggestion
work?

regards,
cm

"Maxim S. Shatskih" <maxim@storagecraft.com> wrote in message
news:u7xlydSJHHA.420@TK2MSFTNGP06.phx.gbl...
> Use stdio.h instead.
>
> --
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> maxim@storagecraft.com
> http://www.storagecraft.com
>
> "Carey McMaster" <mcmaster@stargen.com> wrote in message
> news:uI2nMZSJHHA.4384@TK2MSFTNGP03.phx.gbl...
>> Hi,
>>
>> I'm using the winddk (6000) to not only develop a WDF driver, but also a
>> console app that tests out my driver (using IOCTLs). When I include
>> <iostream> in the console app, the ddk compiler can't find it. I did find
>> it
>> in c:\winddk\6000\inc\api\crt\stl70. The test app uses classes and "new"
>> constructs, but I can't seem to include <iostream> for stl::cout and the
>> like.
>>
>> Here is my sources file for the app
>> ==============================================================
>> TARGETNAME=rmgr
>> TARGETTYPE=PROGRAM
>>
>> UMTYPE=console
>> UMENTRY=main
>>
>> USE_MSVCRT=1
>>
>> !if defined(DDKBUILDENV)
>> C_DEFINES = $(C_DEFINES) -DDDKBUILD=1
>> !endif
>>
>> TARGETLIBS=$(SDK_LIB_PATH)\setupapi.lib \
>> $(SDK_LIB_PATH)\user32.lib \
>>
>>
>> INCLUDES=$(INCLUDES);$(DDK_INC_PATH);
>>
>> SOURCES= \
>> rmgr.cpp
>>
>> RUN_WPP= $(SOURCES) #-func:printf(MSG,...)
>>
>> =========================================================
>>
>> thanks in advance for help,
>> cm
>>
>>
>



Re: iostream by Scott

Scott
Thu Dec 21 12:07:15 CST 2006

Try setting

USE_STL=1
STL_VER=70

In your SOURCES. If that doesn't work start defining random things you find
in makefile.new until you either get it to work or decide that it's no
longer worth trying to get it to build in the DDK

-sctt

--
Scott Noone
Software Engineer
OSR Open Systems Resources, Inc.
http://www.osronline.com


"Carey McMaster" <mcmaster@stargen.com> wrote in message
news:%236EaHnSJHHA.2236@TK2MSFTNGP02.phx.gbl...
> stdio.h doesn't know anything about stl::cout? How does your suggestion
> work?
>
> regards,
> cm
>
> "Maxim S. Shatskih" <maxim@storagecraft.com> wrote in message
> news:u7xlydSJHHA.420@TK2MSFTNGP06.phx.gbl...
>> Use stdio.h instead.
>>
>> --
>> Maxim Shatskih, Windows DDK MVP
>> StorageCraft Corporation
>> maxim@storagecraft.com
>> http://www.storagecraft.com
>>
>> "Carey McMaster" <mcmaster@stargen.com> wrote in message
>> news:uI2nMZSJHHA.4384@TK2MSFTNGP03.phx.gbl...
>>> Hi,
>>>
>>> I'm using the winddk (6000) to not only develop a WDF driver, but also a
>>> console app that tests out my driver (using IOCTLs). When I include
>>> <iostream> in the console app, the ddk compiler can't find it. I did
>>> find it
>>> in c:\winddk\6000\inc\api\crt\stl70. The test app uses classes and "new"
>>> constructs, but I can't seem to include <iostream> for stl::cout and the
>>> like.
>>>
>>> Here is my sources file for the app
>>> ==============================================================
>>> TARGETNAME=rmgr
>>> TARGETTYPE=PROGRAM
>>>
>>> UMTYPE=console
>>> UMENTRY=main
>>>
>>> USE_MSVCRT=1
>>>
>>> !if defined(DDKBUILDENV)
>>> C_DEFINES = $(C_DEFINES) -DDDKBUILD=1
>>> !endif
>>>
>>> TARGETLIBS=$(SDK_LIB_PATH)\setupapi.lib \
>>> $(SDK_LIB_PATH)\user32.lib \
>>>
>>>
>>> INCLUDES=$(INCLUDES);$(DDK_INC_PATH);
>>>
>>> SOURCES= \
>>> rmgr.cpp
>>>
>>> RUN_WPP= $(SOURCES) #-func:printf(MSG,...)
>>>
>>> =========================================================
>>>
>>> thanks in advance for help,
>>> cm
>>>
>>>
>>
>
>



Re: iostream by Maxim

Maxim
Thu Dec 21 12:33:09 CST 2006

> stdio.h doesn't know anything about stl::cout?

I mean - use _tprintf() instead.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com


Re: iostream by Carey

Carey
Thu Dec 21 12:38:19 CST 2006

Thanks Scott! It compiles now. I get lots of warnings about c++ exception
handler. It tells me to use /EHcs. Does anyone know where to state this
switch? I find it odd that this capability is included in the kit, though it
seems very few take advantage of it.

Regards,
cm


"Scott Noone" <snoone@osr.com> wrote in message
news:uHV5ZrSJHHA.1280@TK2MSFTNGP04.phx.gbl...
> Try setting
>
> USE_STL=1
> STL_VER=70
>
> In your SOURCES. If that doesn't work start defining random things you
> find in makefile.new until you either get it to work or decide that it's
> no longer worth trying to get it to build in the DDK
>
> -sctt
>
> --
> Scott Noone
> Software Engineer
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
>
> "Carey McMaster" <mcmaster@stargen.com> wrote in message
> news:%236EaHnSJHHA.2236@TK2MSFTNGP02.phx.gbl...
>> stdio.h doesn't know anything about stl::cout? How does your suggestion
>> work?
>>
>> regards,
>> cm
>>
>> "Maxim S. Shatskih" <maxim@storagecraft.com> wrote in message
>> news:u7xlydSJHHA.420@TK2MSFTNGP06.phx.gbl...
>>> Use stdio.h instead.
>>>
>>> --
>>> Maxim Shatskih, Windows DDK MVP
>>> StorageCraft Corporation
>>> maxim@storagecraft.com
>>> http://www.storagecraft.com
>>>
>>> "Carey McMaster" <mcmaster@stargen.com> wrote in message
>>> news:uI2nMZSJHHA.4384@TK2MSFTNGP03.phx.gbl...
>>>> Hi,
>>>>
>>>> I'm using the winddk (6000) to not only develop a WDF driver, but also
>>>> a
>>>> console app that tests out my driver (using IOCTLs). When I include
>>>> <iostream> in the console app, the ddk compiler can't find it. I did
>>>> find it
>>>> in c:\winddk\6000\inc\api\crt\stl70. The test app uses classes and
>>>> "new"
>>>> constructs, but I can't seem to include <iostream> for stl::cout and
>>>> the
>>>> like.
>>>>
>>>> Here is my sources file for the app
>>>> ==============================================================
>>>> TARGETNAME=rmgr
>>>> TARGETTYPE=PROGRAM
>>>>
>>>> UMTYPE=console
>>>> UMENTRY=main
>>>>
>>>> USE_MSVCRT=1
>>>>
>>>> !if defined(DDKBUILDENV)
>>>> C_DEFINES = $(C_DEFINES) -DDDKBUILD=1
>>>> !endif
>>>>
>>>> TARGETLIBS=$(SDK_LIB_PATH)\setupapi.lib \
>>>> $(SDK_LIB_PATH)\user32.lib \
>>>>
>>>>
>>>> INCLUDES=$(INCLUDES);$(DDK_INC_PATH);
>>>>
>>>> SOURCES= \
>>>> rmgr.cpp
>>>>
>>>> RUN_WPP= $(SOURCES) #-func:printf(MSG,...)
>>>>
>>>> =========================================================
>>>>
>>>> thanks in advance for help,
>>>> cm
>>>>
>>>>
>>>
>>
>>
>
>



Re: iostream by Maxim

Maxim
Thu Dec 21 13:03:02 CST 2006

From some live SOURCES file, for a DCOM service EXE based on ATL:

# Exception Handling on stack
USER_C_FLAGS=$(USER_C_FLAGS) /EHsc

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

"Carey McMaster" <mcmaster@stargen.com> wrote in message
news:%23n9lw8SJHHA.3872@TK2MSFTNGP06.phx.gbl...
> Thanks Scott! It compiles now. I get lots of warnings about c++ exception
> handler. It tells me to use /EHcs. Does anyone know where to state this
> switch? I find it odd that this capability is included in the kit, though it
> seems very few take advantage of it.
>
> Regards,
> cm
>
>
> "Scott Noone" <snoone@osr.com> wrote in message
> news:uHV5ZrSJHHA.1280@TK2MSFTNGP04.phx.gbl...
> > Try setting
> >
> > USE_STL=1
> > STL_VER=70
> >
> > In your SOURCES. If that doesn't work start defining random things you
> > find in makefile.new until you either get it to work or decide that it's
> > no longer worth trying to get it to build in the DDK
> >
> > -sctt
> >
> > --
> > Scott Noone
> > Software Engineer
> > OSR Open Systems Resources, Inc.
> > http://www.osronline.com
> >
> >
> > "Carey McMaster" <mcmaster@stargen.com> wrote in message
> > news:%236EaHnSJHHA.2236@TK2MSFTNGP02.phx.gbl...
> >> stdio.h doesn't know anything about stl::cout? How does your suggestion
> >> work?
> >>
> >> regards,
> >> cm
> >>
> >> "Maxim S. Shatskih" <maxim@storagecraft.com> wrote in message
> >> news:u7xlydSJHHA.420@TK2MSFTNGP06.phx.gbl...
> >>> Use stdio.h instead.
> >>>
> >>> --
> >>> Maxim Shatskih, Windows DDK MVP
> >>> StorageCraft Corporation
> >>> maxim@storagecraft.com
> >>> http://www.storagecraft.com
> >>>
> >>> "Carey McMaster" <mcmaster@stargen.com> wrote in message
> >>> news:uI2nMZSJHHA.4384@TK2MSFTNGP03.phx.gbl...
> >>>> Hi,
> >>>>
> >>>> I'm using the winddk (6000) to not only develop a WDF driver, but also
> >>>> a
> >>>> console app that tests out my driver (using IOCTLs). When I include
> >>>> <iostream> in the console app, the ddk compiler can't find it. I did
> >>>> find it
> >>>> in c:\winddk\6000\inc\api\crt\stl70. The test app uses classes and
> >>>> "new"
> >>>> constructs, but I can't seem to include <iostream> for stl::cout and
> >>>> the
> >>>> like.
> >>>>
> >>>> Here is my sources file for the app
> >>>> ==============================================================
> >>>> TARGETNAME=rmgr
> >>>> TARGETTYPE=PROGRAM
> >>>>
> >>>> UMTYPE=console
> >>>> UMENTRY=main
> >>>>
> >>>> USE_MSVCRT=1
> >>>>
> >>>> !if defined(DDKBUILDENV)
> >>>> C_DEFINES = $(C_DEFINES) -DDDKBUILD=1
> >>>> !endif
> >>>>
> >>>> TARGETLIBS=$(SDK_LIB_PATH)\setupapi.lib \
> >>>> $(SDK_LIB_PATH)\user32.lib \
> >>>>
> >>>>
> >>>> INCLUDES=$(INCLUDES);$(DDK_INC_PATH);
> >>>>
> >>>> SOURCES= \
> >>>> rmgr.cpp
> >>>>
> >>>> RUN_WPP= $(SOURCES) #-func:printf(MSG,...)
> >>>>
> >>>> =========================================================
> >>>>
> >>>> thanks in advance for help,
> >>>> cm
> >>>>
> >>>>
> >>>
> >>
> >>
> >
> >
>
>


Re: iostream by Carey

Carey
Thu Dec 21 13:48:59 CST 2006

Thanks Maxim...

I did a world grep and found the actual switch is /EHa
(/EHsc causes warnings about overriding /EHs- and /EHc-)

thanks again!!
regards,
cm

"Maxim S. Shatskih" <maxim@storagecraft.com> wrote in message
news:e9NqiKTJHHA.3264@TK2MSFTNGP02.phx.gbl...
> From some live SOURCES file, for a DCOM service EXE based on ATL:
>
> # Exception Handling on stack
> USER_C_FLAGS=$(USER_C_FLAGS) /EHsc
>
> --
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> maxim@storagecraft.com
> http://www.storagecraft.com
>
> "Carey McMaster" <mcmaster@stargen.com> wrote in message
> news:%23n9lw8SJHHA.3872@TK2MSFTNGP06.phx.gbl...
>> Thanks Scott! It compiles now. I get lots of warnings about c++ exception
>> handler. It tells me to use /EHcs. Does anyone know where to state this
>> switch? I find it odd that this capability is included in the kit, though
>> it
>> seems very few take advantage of it.
>>
>> Regards,
>> cm
>>
>>
>> "Scott Noone" <snoone@osr.com> wrote in message
>> news:uHV5ZrSJHHA.1280@TK2MSFTNGP04.phx.gbl...
>> > Try setting
>> >
>> > USE_STL=1
>> > STL_VER=70
>> >
>> > In your SOURCES. If that doesn't work start defining random things you
>> > find in makefile.new until you either get it to work or decide that
>> > it's
>> > no longer worth trying to get it to build in the DDK
>> >
>> > -sctt
>> >
>> > --
>> > Scott Noone
>> > Software Engineer
>> > OSR Open Systems Resources, Inc.
>> > http://www.osronline.com
>> >
>> >
>> > "Carey McMaster" <mcmaster@stargen.com> wrote in message
>> > news:%236EaHnSJHHA.2236@TK2MSFTNGP02.phx.gbl...
>> >> stdio.h doesn't know anything about stl::cout? How does your
>> >> suggestion
>> >> work?
>> >>
>> >> regards,
>> >> cm
>> >>
>> >> "Maxim S. Shatskih" <maxim@storagecraft.com> wrote in message
>> >> news:u7xlydSJHHA.420@TK2MSFTNGP06.phx.gbl...
>> >>> Use stdio.h instead.
>> >>>
>> >>> --
>> >>> Maxim Shatskih, Windows DDK MVP
>> >>> StorageCraft Corporation
>> >>> maxim@storagecraft.com
>> >>> http://www.storagecraft.com
>> >>>
>> >>> "Carey McMaster" <mcmaster@stargen.com> wrote in message
>> >>> news:uI2nMZSJHHA.4384@TK2MSFTNGP03.phx.gbl...
>> >>>> Hi,
>> >>>>
>> >>>> I'm using the winddk (6000) to not only develop a WDF driver, but
>> >>>> also
>> >>>> a
>> >>>> console app that tests out my driver (using IOCTLs). When I include
>> >>>> <iostream> in the console app, the ddk compiler can't find it. I did
>> >>>> find it
>> >>>> in c:\winddk\6000\inc\api\crt\stl70. The test app uses classes and
>> >>>> "new"
>> >>>> constructs, but I can't seem to include <iostream> for stl::cout and
>> >>>> the
>> >>>> like.
>> >>>>
>> >>>> Here is my sources file for the app
>> >>>> ==============================================================
>> >>>> TARGETNAME=rmgr
>> >>>> TARGETTYPE=PROGRAM
>> >>>>
>> >>>> UMTYPE=console
>> >>>> UMENTRY=main
>> >>>>
>> >>>> USE_MSVCRT=1
>> >>>>
>> >>>> !if defined(DDKBUILDENV)
>> >>>> C_DEFINES = $(C_DEFINES) -DDDKBUILD=1
>> >>>> !endif
>> >>>>
>> >>>> TARGETLIBS=$(SDK_LIB_PATH)\setupapi.lib \
>> >>>> $(SDK_LIB_PATH)\user32.lib \
>> >>>>
>> >>>>
>> >>>> INCLUDES=$(INCLUDES);$(DDK_INC_PATH);
>> >>>>
>> >>>> SOURCES= \
>> >>>> rmgr.cpp
>> >>>>
>> >>>> RUN_WPP= $(SOURCES) #-func:printf(MSG,...)
>> >>>>
>> >>>> =========================================================
>> >>>>
>> >>>> thanks in advance for help,
>> >>>> cm
>> >>>>
>> >>>>
>> >>>
>> >>
>> >>
>> >
>> >
>>
>>
>



Re: iostream by Tim

Tim
Thu Dec 21 23:33:15 CST 2006

"Scott Noone" <snoone@osr.com> wrote:
>
>Try setting
>
>USE_STL=1
>STL_VER=70
>
>In your SOURCES. If that doesn't work start defining random things you find
>in makefile.new until you either get it to work or decide that it's no
>longer worth trying to get it to build in the DDK

I laughted out loud at that. Those are the words of someone who has had
too much real-life experience with build.exe.
--
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.