|
-
Sep 14th, 2001, 04:24 PM
#1
Thread Starter
Addicted Member
-
Sep 14th, 2001, 04:44 PM
#2
Monday Morning Lunatic
As for the includes, in Project Settings you can add another path to the list of include paths for that project (this is per-configuration, by the way).
For CREATING the DLL, you need to use __declspec(dllexport), and __declspec(dllimport) for USING the DLL. This means that you need to define a macro based on the project settings. See the other DLL threads for this
I refuse to tie my hands behind my back and hear somebody say "Bend Over, Boy, Because You Have It Coming To You".
-- Linus Torvalds
-
Sep 15th, 2001, 05:05 AM
#3
Thread Starter
Addicted Member
??? i thought i had done that
I thought i had already put that stuff in:
#ifndef __KEYDLL_H__
#define __KEYDLL_H__
#include <windows.h>
#ifdef _DLL_INTERNAL_
#define DLLEXPORT __declspec(dllexport)
#else
#define DLLEXPORT __declspec(dllimport)
#endif
int DLLEXPORT WINAPI InitHooksDll(HWND hwndMainWindow, int nWinLineHeight);
int DLLEXPORT WINAPI PaintHooksDll(HDC hDC );
int DLLEXPORT WINAPI InstallFilter (int nHookIndex, int nCode );
char DLLEXPORT *szMessageString(int ID);
#endif // __KEYDLL_H__
do i need to put it somewhere else in my code as well?
-
Sep 15th, 2001, 05:20 AM
#4
when you create the dll, it should also create a file named "keydll.lib"
You have to add this file under Linker->Object/Library Modules in the project settings.
All the buzzt
 CornedBee
"Writing specifications is like writing a novel. Writing code is like writing poetry."
- Anonymous, published by Raymond Chen
Don't PM me with your problems, I scan most of the forums daily. If you do PM me, I will not answer your question.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|