Seite 1 von 1

.pro Datei bereit für opensuse build service?

Verfasst: 20. September 2008 22:19
von Vrenn
Hallo!

Ich habe ein kleines Programm geschrieben und sogar gelernt, wie man ein make install für qmake schreiben kann. Allerdings weiß ich nicht, ob dies auch korrekt geschrieben ist und bitte daher um eure Meinung:

Code: Alles auswählen

TEMPLATE = app
CONFIG += qt

#I want to debug on my developer system
unix {
 CONFIG += debug
}
win32 {
 CONFIG += release
}

#Linux pathes
unix {
 INCLUDEPATH += .\
		/usr/include/dcmtk/config\
		/usr/include/dcmtk/dcmdata\
		/usr/include/dcmtk/ofstd\
		/usr/include/dcmtk/dcmimgle\
		/usr/include/dcmtk/dcmimage\
		/usr/include/dcmtk/dcmjpeg\
		/usr/include
#Double entry for my personal build enviroment
 INCLUDEPATH += .\
		../../binary/include/dcmtk/config\
		../../binary/include/dcmtk/dcmdata\
		../../binary/include/dcmtk/ofstd\
		../../binary/include/dcmtk/dcmimgle\
		../../binary/include/dcmtk/dcmimage\
		../../binary/include/dcmtk/dcmjpeg\
		../../binary/include

 LIBS += -L/usr/lib -ldcmdata -ldcmimage\
	-ldcmjpeg -ldcmimgle\
	-lofstd -lijg8\
	-lijg16 -lijg12

#Double entry for my personal build enviroment
 LIBS += -L../../binary/lib -ldcmdata -ldcmimage\
	-ldcmjpeg -ldcmimgle\
	-lofstd -lijg8\
	-lijg16 -lijg12

 DEFINES += HAVE_CONFIG_H

#Makefile installation resources
 target.path = $$(MYDESTDIR)/usr/share/ourDicom #puts the binary to the right place, but what about the images??
 INSTALLS += target
 ourdicomimages.path = $$(MYDESTDIR)/usr/share/ourDicom
 ourdicomimages.files = ./images/
 INSTALLS += ourdicomimages
 startscript.path = $$(MYDESTDIR)/usr/bin
 startscript.files = ./ourDicom.sh
 INSTALLS += startscript
 translations.path = $$(MYDESTDIR)/usr/share/ourDicom
 translations.files = ./*.qm
 INSTALLS += translations
 license.path = $$(MYDESTDIR)/usr/share/ourDicom
 license.files = ./*.txt
 INSTALLS += license
}

#windows pathes
win32 {
 DEFINES += _USE_MATH_DEFINES

 INCLUDEPATH += ./
 INCLUDEPATH += ../../binary/include/dcmtk/config
 INCLUDEPATH += ../../binary/include/dcmtk/dcmdata
 INCLUDEPATH += ../../binary/include/dcmtk/ofstd
 INCLUDEPATH += ../../binary/include/dcmtk/dcmimgle
 INCLUDEPATH += ../../binary/include/dcmtk/dcmimage
 INCLUDEPATH += ../../binary/include/dcmtk/dcmjpeg
 INCLUDEPATH += ../../binary/include

 LIBS += -L../../binary/lib -ldcmdata -ldcmimage -ldcmjpeg -ldcmimgle -lofstd -lijg8 -lijg16 -lijg12
}

#common unix printing system, just on unix...
unix {
 LIBS += -lcups
}

#general libs
LIBS += -math

#defines used in ourDicom code to separate code qt didnt manage to port
unix {
 DEFINES += OS_UNIX
}
win32 {
 DEFINES += OS_WINDOWS
}

DEFINES += QT3_SUPPORT_WARNINGS
#QT += qt3support
# Input
HEADERS += GUI.h dicomNavigator.h GUIdata.h container.h dataSource.h dicomDir.h dicomNavigatorItem.h patient.h study.h series.h image.h frame.h bw.h dicomPresentator.h rgb.h dicomFile.h dicomDisplay.h metaInformation.h quickInfoDialog.h huList.h exportDialog.h filterDialog.h measureInfoDialog.h quickViewNavigator.h quickViewNavigatorItem.h aboutDialog.h printerDialog.h

SOURCES += main.cc GUI.cc dicomNavigator.cc GUIdata.cc container.cc dataSource.cc dicomDir.cc dicomNavigatorItem.cc patient.cc study.cc series.cc image.cc frame.cc bw.cc dicomPresentator.cc rgb.cc dicomFile.cc dicomDisplay.cc metaInformation.cc quickInfoDialog.cc huList.cc exportDialog.cc filterDialog.cc measureInfoDialog.cc quickViewNavigator.cc aboutDialog.cc quickViewNavigatorItem.cc printerDialog.cc

TRANSLATIONS += ourDicom_de.ts
build.opensuse.org beschwert sich beim make install Teil darum, dass der Ordner /usr/share/ourDicom nicht erstellt werden darf. Ist das korrekt, darf ich das oder machen das alle so?
MYDESTDIR ist dazu da um in meinem Gentoo-cvs-Verzeichnis lokal zu installieren.
Auf Opensuse 11 gehts ansich wunderbar.