However, I agree that DCMTK_INSTALL_ETCDIR is not an easy find (as I myself wasn't aware) nor is it self explanatory if it is working differently than the "standard approach" SYSCONFDIR. However, we should of course allow to install it to /usr instead (package maintainers could of course find workarounds if we won't, but this would be stupid) and we do, so, we are practically okay as it is. Still, I would prefer that manually installed software would not mix with the native packages, therefore, defaulting to /usr/local seems reasonable. Michael Onken wrote:Hm, my experience is that 95% of the software source code packages I download and build on my system want to install themselves into /usr/local.I practically never install software by hand ignoring the package manager, that always seemed like a debian thing to me, as a workaround for their outdated packages. I think the /usr/local thing is not standardized but more an informal convention so far. However, DCMTK's default behaviour is meant for those who download DCMTK from the Internet to install their own copy in their Unix system, *not* for the package maintainers. Do you have any examples? I agree that Debian and all others quoted put their own version of DCMTK (and most of their built-in other packages) into /usr/bin, /usr/lib and so on. I remember that some big ones (OpenOffice?) used /opt/ but haven't seen that for some time now. Hm, my experience is that 95% of the software source code packages I download and build on my system want to install themselves into /usr/local. Arch Linux, Debian, Fedora and openSUSE all are dealing with DCMTK that way. Rather, DCMTK is meant to be used as a regular system library most of the time and as such installed to /usr/lib or variants like /usr/lib but hardly ever to /usr/local/. I assume that it is more common to install DCMTK to /usr/local Not sure whether setting the installation prefix to /usr is often done by people that build DCMTK. Windows? I don't think that a Windows user will actually understand all this. SET(DCMTK_INSTALL_MANDIR "share/man" CACHE STRING "Installation sub-directory for man pages.")įinally, the system of "GNU standard installation directories" is certainly a nice thing but what about non-GNU platforms like e.g. SET(DCMTK_INSTALL_HTMDIR "share/doc/dcmtk/html" CACHE STRING "Installation sub-directory for HTML documentation.") SET(DCMTK_INSTALL_DOCDIR "share/doc/dcmtk" CACHE STRING "Installation sub-directory for general documentation.") SET(DCMTK_INSTALL_DATDIR "share/dcmtk" CACHE STRING "Installation sub-directory for sample files and the like.") SET(DCMTK_INSTALL_ETCDIR "etc/dcmtk" CACHE STRING "Installation sub-directory for configuration files.") SET(DCMTK_INSTALL_CMKDIR "cmake" CACHE STRING "Installation sub-directory for CMake files.") SET(DCMTK_INSTALL_CMKDIR "lib/cmake/dcmtk" CACHE STRING "Installation sub-directory for CMake files.") # to different installation paths under Unix- and Windows-based systems # CMake's files (DCMTKTarget.cmake, DCMTKConfigVersion.cmake and DCMTKConfig.cmake) are installed SET(DCMTK_INSTALL_LIBDIR "lib" CACHE STRING "Installation sub-directory for object code libraries.") SET(DCMTK_INSTALL_INCDIR "include" CACHE STRING "Installation sub-directory for header files.") Code: Select all SET(DCMTK_INSTALL_BINDIR "bin" CACHE STRING "Installation sub-directory for binary executables.")
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |