6 Mar
2020
6 Mar
'20
3:33 a.m.
Hi,
I am wondering if there is a way to check how packages were configured
before building.
When you run automatic build of TDE the information how a package was build
is saved in the xxx.build file, but there are so many and to me it does not
look like consistent output.
I want to know if some configuration options were omitted automatically
because some dev packages or libraries are missing.
For example tdebindings reported that c# (recommended mono) is missing and
therefore bindings for c# will not be build, but it builds the rest.
How can I collect and examine this?
thank and regards
---------------------------------------------------------------------
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
6 Mar
6 Mar
8:06 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 2020/03/06 08:33 PM, deloptes wrote:
Hi, I am wondering if there is a way to check how
packages were configured before building.
When you run automatic build of TDE the information how a package was build is saved in
the xxx.build file, but
there are so many and to me it does not look like consistent output.
I want to know if some configuration options were omitted automatically because some dev
packages or libraries are
missing.
For example tdebindings reported that c# (recommended mono) is missing and therefore
bindings for c# will not be
build, but it builds the rest.
How can I collect and examine this?
thank and regards
Hi Emanoil,
since you are building for debian like distros, start from debian/rules file to see the
option passed to make/cmake.
Then you can look at the build log output that will list the options/libraries detected
and missing. It is very detailed
.
Cheers
Michele
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEjhl1z5vbYB3YbFTiKnW3yore1c8FAl5jHdEACgkQKnW3yore
1c8Sgw/9FlH1Ay0w3/rvu668KiOGrWekeP48ILsa+x2J2s3tfccOFXZnmnnusJSr
jqHxq62wyw8vn/ofQvN/vwI5KldJiWKiSRc0W5owRzOjBglL7BkPyysPMO3Li07v
GrOOLQooX9nQjmmVTXqccM1tNkvcJ4gWlEC4h+6Tlyoh9gLDnQJR4y7FllLpG0f9
iHm+UVuYCdIrvwRU08nE+jSunNXibMfrHkSudafMhikwP5/I6GTi/tVu5HtqcF7N
fh90sspDyfZC3ZlCCkdMruxxkCyWttFjEQ+S4SC2P7DXUXt9apvPfuQyRFFw7G7T
DpHmO+WpET+UVCmpJLz73uCpGHKmDbzcoCPEK2uO0UNFJZZIpIApDnLqs8ltZNiA
xdK61Noy3uuwuK4c9udJqc8olRVPZeELtwEppmggoGzldF7O+SBa/F5vtZkiUHv/
bYYxhc9h/AFRsTowyuNLLght9mvEYXAJjiuykUbZel2RQX4fl/rIGQnRgEWS+eDR
ZZ8xdFVZnw+cCxDnky+56zITAeRmJ1PqHTvg5tdJyx24a8QG1ul+/aLdaKTZ14U+
tFnvwk7zjkk2Hv39ONv8VyUr5vhZqRsXJkejXHAK1resyo6SYknPT5x04fVbA2PQ
CsfP5x/5qw3PZFZVy+OKp2T/BS1OSWwXbMyrh/xkmWhZyvcZDUk=
=kAsY
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
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
11:01 p.m.
New subject: [trinity-devel] Re: How to easily check build configuration
Michele Calgaro via trinity-devel wrote:
Hi Emanoil,
since you are building for debian like distros, start from debian/rules
file to see the option passed to make/cmake. Then you can look at the
build log output that will list the options/libraries detected and
missing. It is very detailed . Cheers
Michele
Thank you Michele, but doesn't it look like manual process? Usually the
configure script may or may not print the results of the configuration.
Can this be automated?
---------------------------------------------------------------------
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
7 Mar
7 Mar
11:20 p.m.
New subject: [trinity-devel] Re: How to easily check build configuration
On 2020/03/07 04:01 PM, deloptes wrote:
Thank you Michele, but doesn't it look like manual
process? Usually the
configure script may or may not print the results of the configuration.
Can this be automated?
Hi Emanoil,
not sure to understand what you are looking for then... Perhaps you can explain better
Cheers
Michele
---------------------------------------------------------------------
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
8 Mar
8 Mar
3:13 a.m.
New subject: [trinity-devel] Re: Re: How to easily check build configuration
Michele Calgaro via trinity-devel wrote:
On 2020/03/07 04:01 PM, deloptes 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
Thank you Michele, but doesn't it look like
manual process? Usually the
configure script may or may not print the results of the configuration.
Can this be automated?
Hi Emanoil,
not sure to understand what you are looking for then... Perhaps you can
explain better Cheers
Michele 
3:30 a.m.
New subject: [trinity-devel] Re: Re: How to easily check build configuration
On Sunday 08 of March 2020 11:13:16 deloptes wrote:
Michele Calgaro via trinity-devel wrote:
Here is the fundamental difference between automake × cmake builds.
It is common for automake that there is a choice of "yes / no / auto" - and
these are exactly where it is uncertain what features are actually
included.
For cmake it is usual that there is a choice of "yes / no" - and if option
is set to yes, then building must fail if the conditions are not met - ie,
not found libraries, includes, etc. Therefore, cmake building should give
certainty what the features are actually included.
Dealing with automation verification for automake building is a waste of
time. That's one of the reasons we want to convert everything to CMake.
Verification in CMake should be an essential part that we try to follow. As
I mentioned above, there should apply that when conditions are not met for
the WITH_* and BUILD_* options, building should always fail in the
configuration phase.
Cheers
--
Slávek
On 2020/03/07 04:01 PM, deloptes 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?
Thank you Michele, but doesn't it look like
manual process? Usually
the configure script may or may not print the results of the
configuration.
Can this be automated?
Hi Emanoil,
not sure to understand what you are looking for then... Perhaps you
can explain better Cheers
Michele
1722
days inactive
1724
days old
5 comments
3 participants
participants (3)
-
deloptes -
Michele Calgaro via trinity-devel -
Slávek Banko