Katana_mirror/kde-extraapps
1
0
Fork 0
mirror of https://bitbucket.org/smil3y/kde-extraapps.git synced 2025-02-26 20:03:10 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
kde-extraapps/okular/generators/CMakeLists.txt

116 lines
3 KiB
Text
Raw Normal View History

generic: replace macro_log_feature() with set_package_properties() calls other changes such as syncing properties, updating some of the URLs, adding missing feature information, removing of redundant checks and variables and indentation were done in the process while testing if the changes work as intended. replacing find_package() with macro_optional_find_package() was also done where applicable however it's usage is questionable due to the CMake `CMAKE_DISABLE_FIND_PACKAGE_<PACKAGE>` option. there is a lot to be done, mostly updating package properties so I am thinking of either providing a package properties file (like the MacroLibrary) which sets properties for packages globablly or setting package properties from the CMake modules shipped with kdelibs. the first solution may override properties for packages if other projects define them however a check to ensure that is not done should suffice. the second solution will cover only DESCRIPTION and URL meaning PURPOSE and TYPE will still have to be specified in the build systems. Signed-off-by: Ivailo Monev <xakepa10@laimg.moc>
2020-02-20 23:33:47 +02:00
macro_optional_find_package(PopplerQt4 0.28.0)
set_package_properties(PopplerQt4 PROPERTIES
DESCRIPTION "A PDF rendering library"
URL "http://poppler.freedesktop.org"
PURPOSE "Support for PDF files in Okular"
)
macro_optional_find_package(LibSpectre 0.2)
set_package_properties(LibSpectre PROPERTIES
DESCRIPTION "A PostScript rendering library"
URL "http://libspectre.freedesktop.org/wiki/"
PURPOSE "Support for PS files in Okular"
)
macro_optional_find_package(DjVuLibre 3.5.17)
set_package_properties(DjVuLibre PROPERTIES
DESCRIPTION "A library for dealing with DjVu formatted files"
URL "http://djvulibre.djvuzone.org"
PURPOSE "Support for DjVu files in Okular"
)
import a bunch of important libraries and applications
2014-11-19 02:23:05 +00:00
macro_optional_find_package(TIFF)
generic: replace macro_log_feature() with set_package_properties() calls other changes such as syncing properties, updating some of the URLs, adding missing feature information, removing of redundant checks and variables and indentation were done in the process while testing if the changes work as intended. replacing find_package() with macro_optional_find_package() was also done where applicable however it's usage is questionable due to the CMake `CMAKE_DISABLE_FIND_PACKAGE_<PACKAGE>` option. there is a lot to be done, mostly updating package properties so I am thinking of either providing a package properties file (like the MacroLibrary) which sets properties for packages globablly or setting package properties from the CMake modules shipped with kdelibs. the first solution may override properties for packages if other projects define them however a check to ensure that is not done should suffice. the second solution will cover only DESCRIPTION and URL meaning PURPOSE and TYPE will still have to be specified in the build systems. Signed-off-by: Ivailo Monev <xakepa10@laimg.moc>
2020-02-20 23:33:47 +02:00
set_package_properties(TIFF PROPERTIES
DESCRIPTION "A library for reading and writing TIFF formatted files"
URL "http://www.remotesensing.org/libtiff"
PURPOSE "Support for TIFF files in Okular"
)
import a bunch of important libraries and applications
2014-11-19 02:23:05 +00:00
macro_optional_find_package(Freetype)
generic: replace macro_log_feature() with set_package_properties() calls other changes such as syncing properties, updating some of the URLs, adding missing feature information, removing of redundant checks and variables and indentation were done in the process while testing if the changes work as intended. replacing find_package() with macro_optional_find_package() was also done where applicable however it's usage is questionable due to the CMake `CMAKE_DISABLE_FIND_PACKAGE_<PACKAGE>` option. there is a lot to be done, mostly updating package properties so I am thinking of either providing a package properties file (like the MacroLibrary) which sets properties for packages globablly or setting package properties from the CMake modules shipped with kdelibs. the first solution may override properties for packages if other projects define them however a check to ensure that is not done should suffice. the second solution will cover only DESCRIPTION and URL meaning PURPOSE and TYPE will still have to be specified in the build systems. Signed-off-by: Ivailo Monev <xakepa10@laimg.moc>
2020-02-20 23:33:47 +02:00
set_package_properties(Freetype PROPERTIES
DESCRIPTION "A font rendering engine"
URL "http://www.freetype.org"
PURPOSE "Provides freetype font support in the Okular DVI generator"
)
import a bunch of important libraries and applications
2014-11-19 02:23:05 +00:00
macro_optional_find_package(JPEG)
generic: replace macro_log_feature() with set_package_properties() calls other changes such as syncing properties, updating some of the URLs, adding missing feature information, removing of redundant checks and variables and indentation were done in the process while testing if the changes work as intended. replacing find_package() with macro_optional_find_package() was also done where applicable however it's usage is questionable due to the CMake `CMAKE_DISABLE_FIND_PACKAGE_<PACKAGE>` option. there is a lot to be done, mostly updating package properties so I am thinking of either providing a package properties file (like the MacroLibrary) which sets properties for packages globablly or setting package properties from the CMake modules shipped with kdelibs. the first solution may override properties for packages if other projects define them however a check to ensure that is not done should suffice. the second solution will cover only DESCRIPTION and URL meaning PURPOSE and TYPE will still have to be specified in the build systems. Signed-off-by: Ivailo Monev <xakepa10@laimg.moc>
2020-02-20 23:33:47 +02:00
set_package_properties(JPEG PROPERTIES
DESCRIPTION "A library for reading and writing JPEG image files"
URL "http://www.ijg.org"
PURPOSE "Support fof PalmDB documents in Okular"
)
import a bunch of important libraries and applications
2014-11-19 02:23:05 +00:00
macro_optional_find_package(ZLIB)
generic: replace macro_log_feature() with set_package_properties() calls other changes such as syncing properties, updating some of the URLs, adding missing feature information, removing of redundant checks and variables and indentation were done in the process while testing if the changes work as intended. replacing find_package() with macro_optional_find_package() was also done where applicable however it's usage is questionable due to the CMake `CMAKE_DISABLE_FIND_PACKAGE_<PACKAGE>` option. there is a lot to be done, mostly updating package properties so I am thinking of either providing a package properties file (like the MacroLibrary) which sets properties for packages globablly or setting package properties from the CMake modules shipped with kdelibs. the first solution may override properties for packages if other projects define them however a check to ensure that is not done should suffice. the second solution will cover only DESCRIPTION and URL meaning PURPOSE and TYPE will still have to be specified in the build systems. Signed-off-by: Ivailo Monev <xakepa10@laimg.moc>
2020-02-20 23:33:47 +02:00
set_package_properties(ZLIB PROPERTIES
DESCRIPTION "General purpose data compression library"
URL "http://www.zlib.net"
PURPOSE "Support for Plucker files in Okular"
)
import a bunch of important libraries and applications
2014-11-19 02:23:05 +00:00
macro_optional_find_package(EPub)
generic: replace macro_log_feature() with set_package_properties() calls other changes such as syncing properties, updating some of the URLs, adding missing feature information, removing of redundant checks and variables and indentation were done in the process while testing if the changes work as intended. replacing find_package() with macro_optional_find_package() was also done where applicable however it's usage is questionable due to the CMake `CMAKE_DISABLE_FIND_PACKAGE_<PACKAGE>` option. there is a lot to be done, mostly updating package properties so I am thinking of either providing a package properties file (like the MacroLibrary) which sets properties for packages globablly or setting package properties from the CMake modules shipped with kdelibs. the first solution may override properties for packages if other projects define them however a check to ensure that is not done should suffice. the second solution will cover only DESCRIPTION and URL meaning PURPOSE and TYPE will still have to be specified in the build systems. Signed-off-by: Ivailo Monev <xakepa10@laimg.moc>
2020-02-20 23:33:47 +02:00
set_package_properties(EPub PROPERTIES
DESCRIPTION "A library for reading EPub documents"
URL "http://sourceforge.net/projects/ebook-tools"
PURPOSE "Support for EPub documents in Okular"
)
import a bunch of important libraries and applications
2014-11-19 02:23:05 +00:00
macro_optional_find_package(QMobipocket)
generic: replace macro_log_feature() with set_package_properties() calls other changes such as syncing properties, updating some of the URLs, adding missing feature information, removing of redundant checks and variables and indentation were done in the process while testing if the changes work as intended. replacing find_package() with macro_optional_find_package() was also done where applicable however it's usage is questionable due to the CMake `CMAKE_DISABLE_FIND_PACKAGE_<PACKAGE>` option. there is a lot to be done, mostly updating package properties so I am thinking of either providing a package properties file (like the MacroLibrary) which sets properties for packages globablly or setting package properties from the CMake modules shipped with kdelibs. the first solution may override properties for packages if other projects define them however a check to ensure that is not done should suffice. the second solution will cover only DESCRIPTION and URL meaning PURPOSE and TYPE will still have to be specified in the build systems. Signed-off-by: Ivailo Monev <xakepa10@laimg.moc>
2020-02-20 23:33:47 +02:00
set_package_properties(QMobipocket PROPERTIES
DESCRIPTION "A library for reading Mobipocket documents"
URL "https://projects.kde.org/projects/kde/kdegraphics/kdegraphics-mobipocket"
PURPOSE "Support for Mobipocket documents in Okular"
)
macro_optional_find_package(QCA2 2.0.0)
set_package_properties(QCA2 PROPERTIES
DESCRIPTION "Qt Cryptographic Architecture"
URL "https://github.com/fluxer/qca"
PURPOSE "Support for encrypted OpenDocument Text documents in Okular"
)
import a bunch of important libraries and applications
2014-11-19 02:23:05 +00:00
# let's enable the generators properly configured
generic: replace macro_log_feature() with set_package_properties() calls other changes such as syncing properties, updating some of the URLs, adding missing feature information, removing of redundant checks and variables and indentation were done in the process while testing if the changes work as intended. replacing find_package() with macro_optional_find_package() was also done where applicable however it's usage is questionable due to the CMake `CMAKE_DISABLE_FIND_PACKAGE_<PACKAGE>` option. there is a lot to be done, mostly updating package properties so I am thinking of either providing a package properties file (like the MacroLibrary) which sets properties for packages globablly or setting package properties from the CMake modules shipped with kdelibs. the first solution may override properties for packages if other projects define them however a check to ensure that is not done should suffice. the second solution will cover only DESCRIPTION and URL meaning PURPOSE and TYPE will still have to be specified in the build systems. Signed-off-by: Ivailo Monev <xakepa10@laimg.moc>
2020-02-20 23:33:47 +02:00
if(PopplerQt4_FOUND)
add_subdirectory(poppler)
endif()
import a bunch of important libraries and applications
2014-11-19 02:23:05 +00:00
generic: replace macro_log_feature() with set_package_properties() calls other changes such as syncing properties, updating some of the URLs, adding missing feature information, removing of redundant checks and variables and indentation were done in the process while testing if the changes work as intended. replacing find_package() with macro_optional_find_package() was also done where applicable however it's usage is questionable due to the CMake `CMAKE_DISABLE_FIND_PACKAGE_<PACKAGE>` option. there is a lot to be done, mostly updating package properties so I am thinking of either providing a package properties file (like the MacroLibrary) which sets properties for packages globablly or setting package properties from the CMake modules shipped with kdelibs. the first solution may override properties for packages if other projects define them however a check to ensure that is not done should suffice. the second solution will cover only DESCRIPTION and URL meaning PURPOSE and TYPE will still have to be specified in the build systems. Signed-off-by: Ivailo Monev <xakepa10@laimg.moc>
2020-02-20 23:33:47 +02:00
if(LibSpectre_FOUND)
add_subdirectory(spectre)
endif()
import a bunch of important libraries and applications
2014-11-19 02:23:05 +00:00
generic: replace macro_log_feature() with set_package_properties() calls other changes such as syncing properties, updating some of the URLs, adding missing feature information, removing of redundant checks and variables and indentation were done in the process while testing if the changes work as intended. replacing find_package() with macro_optional_find_package() was also done where applicable however it's usage is questionable due to the CMake `CMAKE_DISABLE_FIND_PACKAGE_<PACKAGE>` option. there is a lot to be done, mostly updating package properties so I am thinking of either providing a package properties file (like the MacroLibrary) which sets properties for packages globablly or setting package properties from the CMake modules shipped with kdelibs. the first solution may override properties for packages if other projects define them however a check to ensure that is not done should suffice. the second solution will cover only DESCRIPTION and URL meaning PURPOSE and TYPE will still have to be specified in the build systems. Signed-off-by: Ivailo Monev <xakepa10@laimg.moc>
2020-02-20 23:33:47 +02:00
add_subdirectory(kimgio)
import a bunch of important libraries and applications
2014-11-19 02:23:05 +00:00
generic: replace macro_log_feature() with set_package_properties() calls other changes such as syncing properties, updating some of the URLs, adding missing feature information, removing of redundant checks and variables and indentation were done in the process while testing if the changes work as intended. replacing find_package() with macro_optional_find_package() was also done where applicable however it's usage is questionable due to the CMake `CMAKE_DISABLE_FIND_PACKAGE_<PACKAGE>` option. there is a lot to be done, mostly updating package properties so I am thinking of either providing a package properties file (like the MacroLibrary) which sets properties for packages globablly or setting package properties from the CMake modules shipped with kdelibs. the first solution may override properties for packages if other projects define them however a check to ensure that is not done should suffice. the second solution will cover only DESCRIPTION and URL meaning PURPOSE and TYPE will still have to be specified in the build systems. Signed-off-by: Ivailo Monev <xakepa10@laimg.moc>
2020-02-20 23:33:47 +02:00
if(DjVuLibre_FOUND)
add_subdirectory(djvu)
endif()
import a bunch of important libraries and applications
2014-11-19 02:23:05 +00:00
add_subdirectory(dvi)
if(TIFF_FOUND)
generic: replace macro_log_feature() with set_package_properties() calls other changes such as syncing properties, updating some of the URLs, adding missing feature information, removing of redundant checks and variables and indentation were done in the process while testing if the changes work as intended. replacing find_package() with macro_optional_find_package() was also done where applicable however it's usage is questionable due to the CMake `CMAKE_DISABLE_FIND_PACKAGE_<PACKAGE>` option. there is a lot to be done, mostly updating package properties so I am thinking of either providing a package properties file (like the MacroLibrary) which sets properties for packages globablly or setting package properties from the CMake modules shipped with kdelibs. the first solution may override properties for packages if other projects define them however a check to ensure that is not done should suffice. the second solution will cover only DESCRIPTION and URL meaning PURPOSE and TYPE will still have to be specified in the build systems. Signed-off-by: Ivailo Monev <xakepa10@laimg.moc>
2020-02-20 23:33:47 +02:00
add_subdirectory(tiff)
endif()
import a bunch of important libraries and applications
2014-11-19 02:23:05 +00:00
add_subdirectory(xps)
add_subdirectory(ooo)
add_subdirectory(fictionbook)
add_subdirectory(comicbook)
add_subdirectory(fax)
if(JPEG_FOUND AND ZLIB_FOUND)
generic: replace macro_log_feature() with set_package_properties() calls other changes such as syncing properties, updating some of the URLs, adding missing feature information, removing of redundant checks and variables and indentation were done in the process while testing if the changes work as intended. replacing find_package() with macro_optional_find_package() was also done where applicable however it's usage is questionable due to the CMake `CMAKE_DISABLE_FIND_PACKAGE_<PACKAGE>` option. there is a lot to be done, mostly updating package properties so I am thinking of either providing a package properties file (like the MacroLibrary) which sets properties for packages globablly or setting package properties from the CMake modules shipped with kdelibs. the first solution may override properties for packages if other projects define them however a check to ensure that is not done should suffice. the second solution will cover only DESCRIPTION and URL meaning PURPOSE and TYPE will still have to be specified in the build systems. Signed-off-by: Ivailo Monev <xakepa10@laimg.moc>
2020-02-20 23:33:47 +02:00
add_subdirectory(plucker)
endif()
import a bunch of important libraries and applications
2014-11-19 02:23:05 +00:00
generic: replace macro_log_feature() with set_package_properties() calls other changes such as syncing properties, updating some of the URLs, adding missing feature information, removing of redundant checks and variables and indentation were done in the process while testing if the changes work as intended. replacing find_package() with macro_optional_find_package() was also done where applicable however it's usage is questionable due to the CMake `CMAKE_DISABLE_FIND_PACKAGE_<PACKAGE>` option. there is a lot to be done, mostly updating package properties so I am thinking of either providing a package properties file (like the MacroLibrary) which sets properties for packages globablly or setting package properties from the CMake modules shipped with kdelibs. the first solution may override properties for packages if other projects define them however a check to ensure that is not done should suffice. the second solution will cover only DESCRIPTION and URL meaning PURPOSE and TYPE will still have to be specified in the build systems. Signed-off-by: Ivailo Monev <xakepa10@laimg.moc>
2020-02-20 23:33:47 +02:00
if(EPub_FOUND)
add_subdirectory(epub)
endif()
import a bunch of important libraries and applications
2014-11-19 02:23:05 +00:00
add_subdirectory(txt)
generic: replace macro_log_feature() with set_package_properties() calls other changes such as syncing properties, updating some of the URLs, adding missing feature information, removing of redundant checks and variables and indentation were done in the process while testing if the changes work as intended. replacing find_package() with macro_optional_find_package() was also done where applicable however it's usage is questionable due to the CMake `CMAKE_DISABLE_FIND_PACKAGE_<PACKAGE>` option. there is a lot to be done, mostly updating package properties so I am thinking of either providing a package properties file (like the MacroLibrary) which sets properties for packages globablly or setting package properties from the CMake modules shipped with kdelibs. the first solution may override properties for packages if other projects define them however a check to ensure that is not done should suffice. the second solution will cover only DESCRIPTION and URL meaning PURPOSE and TYPE will still have to be specified in the build systems. Signed-off-by: Ivailo Monev <xakepa10@laimg.moc>
2020-02-20 23:33:47 +02:00
if(QMobipocket_FOUND)
add_subdirectory(mobipocket)
import a bunch of important libraries and applications
2014-11-19 02:23:05 +00:00
endif()
Reference in a new issue Copy permalink