Why not do a FIND_PROGRAM on dpkg and use it if it's there (and you're not cross-compiling...) but keep the old logic in place if there is no dpkg....?<br><br><div class="gmail_quote">On Fri, Mar 28, 2008 at 11:37 AM, Mathieu Malaterre <<a href="mailto:mathieu.malaterre@gmail.com">mathieu.malaterre@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br>
<br>
Please consider the attached patch for inclusion in cmake 2.6.0.<br>
Without the patch it puts the responsability on each packager to<br>
properly set the architecture to create valid debian package. Instead<br>
getting the result from dpkg --print-architecture is the correct way.<br>
<br>
Right now I have to do:<br>
<br>
IF(${CMAKE_SYSTEM_PROCESSOR} STREQUAL "x86_64")<br>
SET(CPACK_DEBIAN_PACKAGE_ARCHITECTURE amd64)<br>
ELSEIF(${CMAKE_SYSTEM_PROCESSOR} STREQUAL "i686")<br>
SET(CPACK_DEBIAN_PACKAGE_ARCHITECTURE i386)<br>
ENDIF(${CMAKE_SYSTEM_PROCESSOR} STREQUAL "x86_64")<br>
<br>
<br>
The initial plan was not to rely on any tool to create debian<br>
package, but since NSIS packager rely on NSIS exe, I believe relying<br>
on the presence of dpkg is relatively weak.<br>
<br>
Thanks<br>
<br>
--<br>
<font color="#888888">Mathieu<br>
</font><br>_______________________________________________<br>
CMake mailing list<br>
<a href="mailto:CMake@cmake.org">CMake@cmake.org</a><br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br></blockquote></div><br>