VS2005 failing to export functiions

I have this odd problem. Im using RapidMind to speed up some calculations. I wrapped my functions in a DLL, but for some reason the functions are not being exported. The project compiles fine, but when i try to load the library from LabView, the function doesnt show up. I used __declspec(dllexport) in the function declaration.

example -

Code:

---


__declspec(dllexport) void Foo(float* Input , float* Output){
   
    // rapidmind code goes here
 
    return;
    }

---

If it's in a C++ file, then the name will get mangled - in which case you would use this:

Code:

---

extern "C" __declspec(dllexport)
void Foo(float* Input , float* Output) {...}

---

You may also need to check the calling convention expected by LabView.

gg

Then again, you might want name mangling - otherwise you can't overload and export functions.
If you're trying to import functions from a C++ project, then name mangling is perfectly fine. If you use C or some other non-trivial method, then you might want to try "extern C" (but you can't export overloaded functions if you do).

no, the oblem is that the function isnt being exported, mangled or not. Its just not showing up at all. I tried adign teh extern "C" but it made no difference.

That's the way you do export functions. That or the the function name in a .def file.
If it doesn't work, then the problem must lie in the application you're using to probe for exported functions.
And as mentioned, try other calling conventions.

Thats just it, there isnt a problem with LabView, it can access exported functions is all the 9other DLL's, therefor the problem must lie with the DLL itself. And as I said, i alreay tried the other calling conventions. Labview actualyl shows you the list of exported functions, so it woudlnt matter what the callign convention was anyway, it woudl still show up. Its simply not being exported for some reason.

If you can access the exported functions in the DLL from another application, then the problem DOES lie in LabView. Try it.

Use depends.exe from the PlatformSDK or VisualStudio to inspect the exported symbols from your DLL.

gg

My only guess is you lack this:

Code:

---

#ifdef DLL_EXPORTS
#define DLL_API __declspec(dllexport)
#else
#define DLL_API __declspec(dllimport)
#endif

---

This

Code:

---


__declspec(dllexport) void Foo(float* Input , float* Output){
   
    // rapidmind code goes here
 
    return;
    }

---

Will always export the function but it will never import it. With what I showed you when you build the DLL you define DLL_EXPORTS in your pre-processor and DLL_API is then export. When you are using the header for the DLL then you do not define DLL_EXPORTS and DLL_API then becomes import.

Labview doesnt use header files. My guess is it uses the LoadLibrary() functon and accesses the DLL's export table. As it turns out, what was happening is that VS2005 kept using the old OBJ rather than rebuilding, even though changes where made. Obviously the old obj didnt have any functions in it.

Erm, OBJ? An obj file is an intermediate compiler file, nothing more. Lib files contain export tables for DLLs and the DLLs contain the actual functions (+ export table).

DLL contains the export table. An "export lib" allows you to dynamically link to a DLL without having to use LoadLibrary() and GetProcAddress() explicitly.

gg