dllexport

Assuming I have these two files: Header.h class DLL ExportClass{ public: ExportClass(); static int test; }; Source.cpp #ifdef EXPORT #define DLL __declspec(dllexport) #else #define DLL __declspec(dllimport) #endif #include "Header.h" int ExportClass::test = 0; ExportClass::ExportClass(){ } And I won't define EXPORT (to import a already exported class with a static member), why do I get these warnings: 1>source.cpp(11): warning C4273: 'test' : inconsistent dll linkage 1> header.h(4) : see previous definition of 'public: static int ExportClass::test' 1>source.cpp(13): warning C4273: 'ExportClass

Is there any way to automatically generate the DEF file for a DLL in Visual Studio? I've always just manually created them before, but there's gotta be an easier way. user2577497 I have found a place to generate the .DEF file for you here: expdef - def file generator This works amazing and has a list of options you could also generate besides the method names of the functions and symbols. 0xC0000022L Simply put: write a script that suits your needs. I for one created a small Perl script at some to create a .def file from an existing DLL that would then be used to create an import library (

I just created a DLL for my boss in MSVC++2010. I selected "New Win32 DLL" with option "Export symbols", so, everything is completely standard. There are some predefined exports in the new project files, a class, its constructor, a global function and variable with bogus values and a file dllmain.cpp with an APIENTRY function. I changed nothing yet. Now my boss wants to use the exported things in his VB6 project. He started a VB6 project, did menu "Project" - "Links" (translated from German to English, so it might be somewhat different but I'm sure you know what I mean) and selected a DLL file

I am converting an ATL-based static library to a DLL and am getting the following warning on any exported classes that use the ATL CString class (found in atlstr.h): warning C4251: 'Foo::str_' : class 'ATL::CStringT' needs to have dll-interface to be used by clients of class 'Foo' I am correctly declaring the Foo class as exported via __declspec(dllexport) . Is this a warning I can safely ignore or am I doing something wrong? The DLL project settings are set to dynamically link with ATL, but this doesn't seem to make any difference. For example: #ifdef DLLTEST_EXPORTS #define DLLTEST_API _

I have a running Inno Setup script, wherein I use innocallback.dll by Sherlock Software. This DLL wraps a procedure of mine so that it can be passed to a C# DLL. I don't want to use this DLL, I want to call my exported C# method directly and pass to it the callback procedure. My question is: How can I pass my Inno Setup procedure ( @mycallback ) to my C# DLL so that I can use it as my delegate / UnmanagedFunctionPointer ? As I said this code works, but I want to use as little external DLL's as possible. Here is my code: Inno Setup Script type TTimerProc=procedure(); TProgressCallback=procedure

I have an executable written in C that has some functions in it that I would like to use from a c# application. I have written plenty of dlls before and was able to use functions in them by prepending __declspec(dllexport) to the function declaration. Can I do this from an executable? will the executable actually export the function? Yes you can! Yes the executable will export the functions. This is not done very often, but it works pretty good. According the Specification ( http://msdn.microsoft.com/en-us/gg463119.aspx ) of the Executable, there is no difference between DLL and Executable as

http://msdn.microsoft.com/en-us/library/9h658af8.aspx MSDN says I can export function from the library with __declspec(dllexport) but how can I load this library in my executable? I've got an exported function in DLL: __declspec(dllexport) void myfunc(){} And now I would like to use it in my executable: __declspec(dllimport) void myfunc(void); But how my program will know where to find this function? CharlesB This is the compiler/linker job, it's done automatically as long as you include the .lib in the Linker options provide the DLL at runtime so that it's found by the exe The .lib file is