利用C語言創(chuàng)建和使用DLL文件

imelee 2015-04-25

展開全文

有感于講C語言的DLL文件的文章很少，自己查了半天，寫了這么個非常簡單的教程。自己也是摸C語言不久，依然感覺處于編程苦手的階段。

1）為什么使用DLL文件

C語言復(fù)用代碼有很多的形式，利用動態(tài)鏈接庫（DLL）來復(fù)用代碼也是一種很有效的做法。使用DLL相比利用靜態(tài)庫來復(fù)用代碼有幾點不同：

a. 可以不用寫 header File，但是在編譯過程中需要在編譯器里把文件鏈接起來；

b. 更加靈活，可以只改動和編譯DLL文件的內(nèi)容，而不用對程序其他部分進行修改；

c. 利用DLL文件可以方便地與其他語言進行鏈接（比如Python）。

2）創(chuàng)建DLL及C語言調(diào)用程序

目前看來，創(chuàng)建 DLL 文件和創(chuàng)建普通c語言文件沒有什么不同。創(chuàng)建 C++ 的 DLL 文件要更復(fù)雜一些，C 則相對簡單。照著 C 代碼的格式寫一個文件（注：C++ 似乎會不同，微軟就有教程，可以查閱VS的幫助文檔）。

以下是一個實例，文件名為 TestDll.c

//TestDll.c 

#include <</font>stdio.h>

int hello()

{

    printf
("Hello from DLL\n");

}

int SumNumbers(int a, int b)

{

    int
c;

    c=a+b;

    return
c;

}

然后寫一個主程序來調(diào)用，文件名為 UseTestDll.c

//UseTestDLL.c 

#include <</font>stdio.h>

int main()

{

    hello();

    hello();

    int
a=2,b=3;

    int
c;

    c=SumNumbers(a,
b);

    printf
("c= %d.\n",c);

}

搞定。

3）編譯及運行

測試使用的是 MinGW 下的 gcc 編譯器。

a. 編譯 DLL 文件

先將 c 文件編譯成 o 文件，然后再講 o 文件編譯成為 DLL 文件，在 cmd 里面代碼如下：

gcc -c TestDLL.c

gcc -shared -o TestDll.dll TestDll.o

這樣就得到了 TestDll.dll 文件，如果文件多的話可以寫個Batch文件來搞定。

b. 編譯使用文件

gcc -o UseTestDll
UseTestDll.c -L./ -lTestDll

這樣就得到了 UseTestDll.exe 文件。UseTestDll.exe 和 TestDll.dll 形成了程序的兩個部分，缺一不可。

運行一下：

4）在Python中使用已有的Dll文件

DLL文件一樣可以在Python中使用。我們可以利用python自帶的ctypes模塊（python2.5后自帶，之前得自己再去下，不過現(xiàn)在也沒有人用2.5之前的了吧）。下面是一個示例文件，文件名為UseCDll.py

from ctypes
import *

# Simple Test on c_int object

i=c_int(5)

print i

print i.value

i.value=10

print i.value

# Import Dll

TestDll=CDLL('TestDll.dll')

# Test Print Function

TestDll.hello()

# Test variable dilivery

a=c_int(4)

b=c_int(6)

c=TestDll.SumNumbers(a,b)

print c

函數(shù)說明：

c_int() 在python下創(chuàng)建c的int類型對象，因為python的數(shù)據(jù)類型和c的數(shù)據(jù)類型需要轉(zhuǎn)換
CDLL() 讀入DLL文件，并將其轉(zhuǎn)化為一個對象，利用對象.函數(shù) 的形式調(diào)用DLL里面的函數(shù)

運行一下：

成功實現(xiàn)了在Python下使用DLL文件，這種方法可以減少代碼重復(fù)開發(fā)，同時由于C的速度比Python大很多，還可以用這個方法對Python進行加速。

5）APPENDIX

關(guān)于gcc編譯命令的一些說明，來自gcc官方文檔。

-shared

Produce a shared object which can then be linked with other objects to form an executable. Not all systems support this option. For predictable results, you must also specify the same set of options used for compilation (‘-fpic’, '-fPIC’, or model suboptions) when you specify this linker option.¹

1 On some systems, ‘gcc -shared’ needs to build supplementary stub code for constructors to work. On

multi-libbed systems, ‘gcc -shared’ must select the correct support libraries to link against. Failing to

supply the correct flags may lead to subtle defects. Supplying them in cases where they are not necessary

is innocuous

-Ldir

Add directory dir to the list of directories to be searched for ‘-l’.

-o file

Write output to file. This is the same as specifying file as the second non-option argument to cpp. gcc has a different interpretation of a second non-option argument, so you must use ‘-o’ to specify the output file.

-c

Compile or assemble the source files, but do not link. The linking stage simplyis not done. The ultimate output is in the form of an object file for each source file. By default, the object file name for a source file is made by replacing the suffix ‘.c’, ‘.i’, ‘.s’, etc., with ‘.o’.

Unrecognized input files, not requiring compilation or assembly, are ignored.

-llibrary

-l library

Search the library named library when linking. (The second alternative with the library as a separate argument is only for POSIX compliance and is not recommended.) It makes a difference where in the command you write this option; the linker searches and processes libraries and object files in the order they are specified. Thus, ‘foo.o -lz bar.o’ searches library ‘z’ after file ‘foo.o’ but before

‘bar.o’. If ‘bar.o’ refers to functions in ‘z’, those functions may not be loaded. The linker searches a standard list of directories for the library, which is actually a file named ‘liblibrary.a’. The linker then uses this file as if it had been specified precisely by name.

The directories searched include several standard system directories plus any that you specify with ‘-L’.

Normally the files found this way are library files—archive files whose members are object files. The linker handles an archive file by scanning through it for members which define symbols that have so far been referenced but not defined.

But if the file that is found is an ordinary object file, it is linked in the usual fashion. The only difference between using an ‘-l’ option and specifying a file name is that ‘-l’ surrounds library with ‘lib’ and ‘.a’ and searches several directories.