tags:

views:

73

answers:

0
+1  Q: 

Missing entry point for x64 DLL project

I create a simple dll project with visual studio 2010 wizard, haven't filled any code.

When I build it on Win32 platform, everything works fine. The problem is when I switch to x64 platform, there is Link error.

2>LINK : fatal error LNK1561: entry point must be defined

The export marco has been define in the stdafx.h like:

#define AECCDBVALIGNMENT_EXPORTS

Anyone can help?

[Close] Resolved by creating the correct x64 platform settings.

related questions

Is it feasible to compile Python to machine code?
What does the "no version information available" error from linux dynamic linker mean?
Visual Studios Link.exe error: "extra operand"
Why does fatal error "LNK1104: cannot open file 'C:\Program.obj'" occur when I compile a C++ project in Visual Studio?
fatal error C1900: Il mismatch between 'P1' version '20060201' and 'P2' version '20050411'
Link error when compiling gcc atomic operation in 32-bit mode
Problem Linking "static" Methods in C++
How to release .Net apps without bundling .Net framework?
Why Am I Getting Link Errors When Calling Function in Math.h?
crti.o file missing
How best to alleviate scenarios that trigger non-incremental linking (MSVS)
Linking .Net Assemblies
Delphi Out of resources
Why do we need extern "C"{ #include <foo.h> } in C++?
Visibility of template specialization of C++ function
VS 2005 & 2008 library linking
What's the best tool to graphically display memory layout from a .map file?
Is there a way to parse a dependency tree from a build script output?
Linker order - GCC
Mixing C/C++ Libraries
Linking statically in C#
How do I make a fully statically linked .exe with Visual Studio Express 2005 ?
Best practices for debugging linking errors.
What libraries do I need to link my mixed-mode application to?
Link issues (VC6)