Re: Macro calling kernel function

David wrote
(in article
<1122601305.260026.300550@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>):

> Thanks Walter.
> My problem is, I have C file and .h file in my driver
> If I define this macro in C file it compiles and links, no problem
> But I define same macro in .h file it throws compile error ..
> undeclared identifier for function name
> I tired including header file for the function but :(
> whats the reason behind that.

I'll hazard a guess. There are types declared in some other
header(s) included in your .c file that you aren't including in
your header file, causing it to fail.

--
Randy Howard (2reply remove FOOBAR)

.

Relevant Pages

  • Compile error after adding #define WPP_GLOBALLOGGER
    ... WPP_CONTROL_GUIDS macro definition. ... I now get the following compile error in only the .cpp file that has the ... When I commend out the #define WPP_GLOBALLOGGER macro, the driver compiles ...
    (microsoft.public.development.device.drivers)
  • Year dependent macros help??? Its quite urgent : )
    ... This is then looked up in the Fieldtrips worksheet and it's macros. ... When the user presses the "Edit a Summer Fieldtrip" button, a macro is ... when I click on the Yes button a compile error message appears ... userform is displayed as intended. ...
    (microsoft.public.excel.misc)
  • Year dependent macros......lengthy but i really need help thx
    ... This is then looked up in the Fieldtrips worksheet and it's macros. ... When the user presses the "Edit a Summer Fieldtrip" button, a macro is ... when I click on the Yes button a compile error message appears ... userform is displayed as intended. ...
    (microsoft.public.excel.misc)
  • Re: Driver Model
    ... If the driver does not contain the appropriate ... > If the MODULE_LICENSEmacro is what determines taint, ... the module is GPL and (after you've shipped ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: Win 2000 Word 2003 Compile error VB
    ... Microsoft Office MVP ... Macro Compile error is displayed as previously noted. ... The display is from the VB debugger which comes up next after ...
    (microsoft.public.word.application.errors)