[trinity-devel] Re: Re: How to easily check build configuration

Michele Calgaro via trinity-devel wrote: I think this was correct, what you understood. For example tdelibs during configuration says -- Found PCSCLITE: /usr/lib/x86_64-linux-gnu/libpcsclite.so -- Checking for one of the modules 'libcryptsetup' -- Performing Test HAVE_NEW_CRYPTSETUP -- Performing Test HAVE_NEW_CRYPTSETUP - Success -- Performing Test HAVE_CRYPTSETUP_GET_TYPE -- Performing Test HAVE_CRYPTSETUP_GET_TYPE - Success -- Found JPEG: /usr/lib/x86_64-linux-gnu/libjpeg.so (found version "62") -- Found PNG: /usr/lib/x86_64-linux-gnu/libpng.so (found version "1.6.36") -- Found TIFF: /usr/lib/x86_64-linux-gnu/libtiff.so (found version "4.1.0") -- Found Jasper: /usr/lib/x86_64-linux-gnu/libjasper.so (found version "1.900.1") in many cases there are conditions in the make system (automake or cmake) that will enable or disable an optional feature if the library is found or not found. How one could know what feature was compiled at the end? --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting