Forum: C++ Nov 10th, 2008 |
| Replies: 2 Views: 433 I'm adding 30 at a time.
The full story is, I once had this problem with DLLs built with MSVC, and fixed it by adding in quants.
Now that I've moved to building with Intel C++ compiler, the... |
Forum: C++ Nov 10th, 2008 |
| Replies: 2 Views: 433 Hi,
I've been experiencing problems when attempting to add resources to a DLL using UpdateResource. I'm adding many images to the DLL, and as soon as the overall image size reaches ~16MB, the DLL... |
Forum: C++ May 10th, 2008 |
| Replies: 6 Views: 1,312 Well, it is also sufficient to place the function body in the same file as the *declaration*.
For example in my case, moving the function body from b.cpp to a.cpp without further changes would be... |
Forum: C++ May 10th, 2008 |
| Replies: 6 Views: 1,312 No, both a.cpp and b.cpp are files that compile into one dll. I did not specify the client to that dll.
Gil. |
Forum: C++ May 9th, 2008 |
| Replies: 6 Views: 1,312 Oh, of course, forgot to mention the __declspec. Well, it is there.
Try out the scenario I depicted and see that although no link problems, a() is not being exported.
Gil. |
Forum: C++ May 9th, 2008 |
| Replies: 6 Views: 1,312 Hi,
(using MS VS2005) Recently I've found that in order for a function to be exported, dllexport *must* be placed in the same file of the function body. E.g. see the following case:
File a.cpp
... |