Error:No Target architecture defined

Question

3.00/5 (2 votes)

See more:

Hi,
I am getting error of "No Target architecture defined" in driver entry. i am trying to write driver entry for wireless miniport in vc++ and wdk on vista plateform. But this error fed up me.
so pls help me out.

1>------ Rebuild All started: Project: DriverMiniport, Configuration: checked Win32 ------
1>Deleting intermediate and output files for project 'DriverMiniport', configuration 'checked|Win32'
1>Compiling...
1>miniport.c
1>c:\winddk\7600.16385.0\inc\ddk\wdm.h(14197) : fatal error C1189: #error : "No target architecture defined"
1>protocol.c
1>c:\winddk\7600.16385.0\inc\ddk\wdm.h(14197) : fatal error C1189: #error : "No target architecture defined"
1>vwifi.c
1>c:\winddk\7600.16385.0\inc\ddk\wdm.h(14197) : fatal error C1189: #error : "No target architecture defined"
1>Generating Code...
1>Build log was saved at "file://e:\DriverMiniport\checked\BuildLog.htm"
1>DriverMiniport - 3 error(s), 0 warning(s)
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========

Posted 23-Mar-10 4:25am

Indrajit kumar

Updated 17-Oct-20 9:20am

Moak

v2

Add a Solution

4 solutions

Solution 57

hi,i met the exactly problem ,can you tell me how you solve it?i'm very appreciate.please......

Posted 10-May-11 22:51pm

markfilan

Solution 58

Here's a decent tutorial on what you're experiencing:
http://mcdermottcybersecurity.com/articles/64-bit-device-driver-development[^]

The DDK files are dependent on environment variables set by other files (read article and you'll see what I mean).

Posted 11-May-11 15:16pm

Albert Holguin

Solution 59

I fixed mine on a project that compile without any problem but after a crash out of nowhere cropped up this same error.

I fixed it by defining _AMD64_ in the Preprocessor definitions

Posted 17-Oct-20 9:21am

Khalfan 10679609

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Eugen Podsypalnikov · Accepted Answer · 2010-03-23T04:46:00

Solution 1

By a double click on a error line
you would see its source... :)

Probably you will need to define something like _X86_
(see, for instance "The Old New Thing: You already know what your target architecture is (or at least you should)"). :)

Posted 23-Mar-10 4:46am

Eugen Podsypalnikov

Updated 23-Mar-10 10:17am

v2