Reviewing CMakeLists.txt, I've noticed: SET(CPACK_DEBIAN_PACKAGE_DEPENDS "libpano13(>=2.9.17), libpost2c2, libglew(>=1.5), freeglut3, libboost-filesystem(>=1.38.0), liblcms1, libopenexr6, libtiff4")
Which appears to set debian package dependencies at >= for certian packages. I assume this can be set for all packages negating the need to hard set any package dependencies and guaranteeing that the build would work so long as the system had >= package. Correct? On Mon, 2010-09-13 at 19:18 +0200, Kornel Benko wrote: > Am Montag 13 September 2010 schrieb Dale Beams: > > Earlier I had indicated using echo from a script to read in the > > dependencies. Someone mentioned that this would not work? Is this > > because of the location of the line in the CMakeLists.txt? > > It was me. > 1.) Location > 2.) Syntax > > > I'd have to dig around for the e-mail, but someone indicated that > > Since most of Hugin programmers are using scripts to build for testing, I'd assume that "-DCPACK_BINARY_PACKAGE-TYPE:BOOL=off" could be set for the default for all packages and then the FAQ could be simplified by removing: cmake ../apsc.hg -DCMAKE_INSTALL_PREFIX=/usr/local -DCPACK_BINARY_DEB:BOOL=ON \ -DCPACK_BINARY_NSIS:BOOL=OFF -DCPACK_BINARY_RPM:BOOL=OFF -DCPACK_BINARY_STGZ:BOOL=OFF \ -DCPACK_BINARY_TBZ2:BOOL=OFF -DCPACK_BINARY_TGZ:BOOL=OFF -DCPACK_BINARY_TZ:BOOL=OFF and replacing it with "cmake ../program.hg -DCMAKE_INSTALL_PREFIX=/usr/local -DCPACK_BINARY_PACKAGE-TYPE:BOOL=on" for each individual build, simplifying that build instruction to one line in the FAQ? I assume the reason it builds all package-types now is a programming default? Dale > > -DCPACK_BINARY_DEB:BOOL=off/on could be set by default within the > > CMakeLists.txt file and then we'd only need to issue the line for the > > particular type of build we were doing, rather than a long list of > > BOOL=off > > Defaults are set in CPack.cmake in _your_ system if not specified by us. > We have to know package management prior to setting our default. > > > libboost-filesystem (& -system) is indicated as optional, but issues > > errors about boost filesystem all the way through the build and > > afterwards during program use about boost not being found. is > > (filesystem & system) truly optional, and if so, is there a way to > > squelch the error and confirm that the build is in fact finding boost? > > True, this looks like it were not optional. > For enblend we should make them required. > > Kornel -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
