1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
| TEMPLATE = lib
CONFIG += qt warn_on
QT -= gui
DEPENDPATH += .
INCLUDEPATH += D:/Programmation/C++/zlib-1.2.7
DEFINES += QUAZIP_BUILD
CONFIG(staticlib): DEFINES += QUAZIP_STATIC
# Input
HEADERS += \
crypt.h\
ioapi.h\
JlCompress.h\
quaadler32.h\
quachecksum32.h\
quacrc32.h\
quazip.h\
quazipfile.h\
quazipfileinfo.h\
quazipnewinfo.h\
quazip_global.h\
unzip.h\
zip.h\
SOURCES += *.c *.cpp
unix:!symbian {
headers.path=$$PREFIX/include/quazip
headers.files=$$HEADERS
target.path=$$PREFIX/lib
INSTALLS += headers target
OBJECTS_DIR=.obj
MOC_DIR=.moc
}
win32 {
headers.path=$$PREFIX/include/quazip
headers.files=$$HEADERS
target.path=$$PREFIX/lib
INSTALLS += headers target
}
symbian {
# Note, on Symbian you may run into troubles with LGPL.
# The point is, if your application uses some version of QuaZip,
# and a newer binary compatible version of QuaZip is released, then
# the users of your application must be able to relink it with the
# new QuaZip version. For example, to take advantage of some QuaZip
# bug fixes.
# This is probably best achieved by building QuaZip as a static
# library and providing linkable object files of your application,
# so users can relink it.
CONFIG += staticlib
CONFIG += debug_and_release
LIBS += -lezip
#Export headers to SDK Epoc32/include directory
exportheaders.sources = $$HEADERS
exportheaders.path = quazip
for(header, exportheaders.sources) {
BLD_INF_RULES.prj_exports += "$$header $$exportheaders.path/$$basename(header)"
}
} |
