Am Montag 13 September 2010 schrieb Dale Beams: > 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?
Not exactly. This _are_ the hardcoded (for now) package dependencies. Not sure
about debian.
(All of them but libpost2c2 are on my system, but not exactly)
Therefore I had now problem to use this package. This is what I had to do
locally, inserting _my_ dependencies:
SET(CPACK_DEBIAN_PACKAGE_DEPENDS "freeglut3 (>=
2.6.0-0),libatlas3gf-base (>= 3.6.0-24),libboost-date-time1.38.0 (>=
1.38.0-6),libboost-thread1.38.0 (>= 1.38.0-6),libexiv2-6 (>=
0.19-1),libglew1.5 (>= 1.5.2-0),libopenexr6 (>= 1.6.1-4.1),libpano13 (>=
2.9.17),libwxgtk2.8-0 (>= 2.8.10.1-0)")
As I somewhere said, this looks totally system-dependent. I don't know, how to
overcome this.
Yuv, maybe we should go back again, until there is some automated method in
cmake itself. This hard-coding
looks not promising for me.
Kornel
--
Kornel Benko
kornel.be...@berlin.de
signature.asc
Description: This is a digitally signed message part.
