|
Hello everyone,
I am using Visual Studio 2005 to develop C++ DLL (in-process COM). There is a setting in Linker --> Input called Module definition file. This setting makes me confused,
1. I have tried that if input a file name (.def), then the generated DLL be larger than the time when we leave the module definition file to empty. Should we leave it empty or non-empty (input a .def file name);
2. What is the function of the module definition file? Should developer write it manually or generated by system.
thanks in advance,
George
|
|
|
|
|
You should create a .def file (always let the machine do it and you can edit it afterwards if you're a serious hacker) if your Dll will be linked into an executable. If it's a purely COM interfaced Dll which will get loaded and the interfaces interogated at run time then I don't think a .def file is going to be needed. It doesn't do any harm though and shouldn't increase the size of your output. If I remeber rightly the exception to this is if you're doing DCOM and want to build proxy/stub dlls for your objects, then you're back to needing a .def file. Either way I'd just switch it on and forget about it unless and until you need it. Good luck.
Nothing is exactly what it seems but everything with seems can be unpicked.
|
|
|
|
|
Thanks Matthew,
I think you mean if I do not hacking the def file itself (I am not doing this), I should just input a file name and let Visual Studio 2005 fill in the content during build process, right?
Could you show me a sample how other component will utilize .def file please?
regards,
George
|
|
|
|
|
Include the .def file created by your Dll project as a source file in an EXE project. Link the EXE project to your Dll and you'll be able to call the Dll functions exported in the .def from the .exe as if they were local functions, no GetProcAddress juggling or anything. Sorry I don't have a ready example handy. I was using this but changed my Dll to generate a .lib file for the case where it is statically linked into an EXE. Check the docs for your compiler version to work out the project-settings/make commands you'll need.
Nothing is exactly what it seems but everything with seems can be unpicked.
|
|
|
|
|
Interesting. I didn't realize you could use the DEF file to do the import on the DLL comusmer consumer side. I've never seen a DLL provider supply a DEF file instead of a LIB file. How did you discover this? I've never seen documentation on a DEF file that said you could use it to import - it's always been mentioned for the export side.
As I said ... interesting. <thoughtful look="">Judy
|
|
|
|
|
Hi Judy,
I want to confirm with you that .DEF technique is a general technique for DLL, and it is not a specific technique for COM DLL (in-process server) only. Right?
regards,
George
|
|
|
|
|
Sorry for the delay in responding, I've been sick for a few days.
George_George wrote: I want to confirm with you that .DEF technique is a general technique for DLL, and it is not a specific technique for COM DLL (in-process server) only. Right?
Yes
|
|
|
|
|
Thanks for considering my question even if you are sick, JudyL_FL.
regards,
George
|
|
|
|
|
Thanks Matthew,
I roughly know your ideas. But a real sample of some URL resources to learn will be better about how other components (which is dependent on the DLL) will utilize the .DEF file.
regards,
George
|
|
|
|
|
|
Thanks Judy,
In my understanding of your reply, you mean .DEF file is used for definition of what functions are exported by the DLL. I am wondering what is the differences between .DEF file and.lib file (import library), which is used to do implicit link when another component is dependent on the DLL?
BTW: could you show me a sample how other component will utilize the .DEF file of the DLL please?
regards,
George
|
|
|
|
|
Note the DEF files are used by DLLs that expose a C interface.
George_George wrote: In my understanding of your reply, you mean .DEF file is used for definition of what functions are exported by the DLL. I am wondering what is the differences between .DEF file and.lib file (import library), which is used to do implicit link when another component is dependent on the DLL?
The DEF file helps control what goes into the LIB file. A function will be listed as an exported function if a) the function has __declspec (dllexport) atrributes or b) the function name is in the DEF file. The LIB file is called an import library because it is given to users of a DLL to link with to resolve the references to functions in the DLL. The user "imports" the library functions into their code so they can link their executable. Use of an import library means that the user does not have to use LoadLibray and GetProcAddress to access the functions exported by the DLL.
George_George wrote: BTW: could you show me a sample how other component will utilize the .DEF file of the DLL please?
Other components do not use the DEF file. It is used by the creator of the DLL to generate his DLL / LIB.
The package provided by a DLL provider should include a .h file, a .lib file and a .dll file. That's all that is required for anyone to use the dll. You actually don't need the .lib but it makes it easier for the users of the dll.
Judy
|
|
|
|
|
Thanks Judy,
I want to confirm that, if I understand your points correctly, .DEF file is used to manage (or I should use the word *impact*) the import library file (.lib), and the other components which is dependent on the DLL should use import library file (.lib) directly other than use .DEF file. Right?
regards,
George
|
|
|
|
|
George_George wrote: I want to confirm that, if I understand your points correctly, .DEF file is used to manage (or I should use the word *impact*) the import library file (.lib), and the other components which is dependent on the DLL should use import library file (.lib) directly other than use .DEF file. Right?
Yes
|
|
|
|
|
Thanks for your confirmation, JudyL_FL!
regards,
George
|
|
|
|
|
Hi all,
I want my mainframe to open in the maximized view defaultly,now i'm using the maximize button to do that,can anybody plz help in this.
Regards..
saravana...
|
|
|
|
|
On the last lines of CMyApp::InitInstance ()
if (!ProcessShellCommand(cmdInfo))
return FALSE;
pMainFrame->ShowWindow(m_nCmdShow | SW_SHOWMAXIMIZED);
pMainFrame->UpdateWindow();
return TRUE;
Greetings.
--------
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
|
|
|
|
|
thanq nelek..,it is working..plz help mi how to get my child window maximised..
thanks in advance
saravana...
|
|
|
|
|
The principle is the same, but you should place it in CChildFrm::PreCreateWindow (...)
take a look into the info of CREATESTRUCT, specially to the cs.style parameter/flag
Greetings.
--------
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
|
|
|
|
|
Looking for ways to generate PDF file in VC++/MFC.
I have found some paid libraries. Is there any other ways or some open sources?
Thank you.
|
|
|
|
|
Haru[^]
Nobody can give you wiser advice than yourself. - Cicero
.·´¯`·->ßRÅhmmÃ<-·´¯`·.
|
|
|
|
|
Thanks.
I'm using google as well but I need to find quick solution so I wanted some good suggestions from nice members like you.
|
|
|
|
|
c07 wrote: I'm using google as well but I need to find quick solution so I wanted some good suggestions
In that case, google for iTextSharp, which I found to be good. But it is to be used only with managed code.
Real men drive manual transmission.
|
|
|
|
|
thanks again..Do you have experience with Acrobat SDK?
|
|
|
|
|
No, I have not worked on Acrobat SDK.
Nobody can give you wiser advice than yourself. - Cicero
.·´¯`·->ßRÅhmmÃ<-·´¯`·.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
