That's it. Thank you very much Alex :-)
D.
--
View this message in context:
http://cmake.3232098.n2.nabble.com/Compatibility-between-cmake-based-directives-and-autoconf-based-directives-tp7583105p7583121.html
Sent from the CMake mailing list archive at Nabble.com.
--
Powered by www.kitware.com
On Tuesday 05 February 2013, DRypl wrote:
> Is there a way how to avoid problems with different declarations of
> directives depending whether
> using autoconf (for a library) and cmake (for my application using that
> library). For example autoconf
> declares "#define HAVE_UNISTD_H 1" while cmake
Is there a way how to avoid problems with different declarations of
directives depending whether
using autoconf (for a library) and cmake (for my application using that
library). For example autoconf
declares "#define HAVE_UNISTD_H 1" while cmake declares "#define
HAVE_UNISTD_H".
Using #cmakedefine