[tpm2] Re: building tpm tools - only built one tool?

[tpm2] Re: building tpm tools - only built one tool?

[Roberts, William C]

[-- Attachment #1: Type: text/plain, Size: 939 bytes --]

Yeah you'll only see one executable. Make install installs symlinks to that executable and then by interogating argv[0] we can figure out what tool to run.

make install will take care of that

You can optionally add DESTDIR to throw them into a non-global user path directory.
DESTDIR='/where/you/want/them'
________________________________
From: Kenneth Goldman <kgoldman(a)us.ibm.com>
Sent: Tuesday, February 16, 2021 3:50 PM
To: tpm2(a)lists.01.org <tpm2(a)lists.01.org>
Subject: [tpm2] building tpm tools - only built one tool?


https://github.com/tpm2-software/tpm2-tools/blob/master/doc/INSTALL.md

says in part

./tools/tpm2_getrandom 4

The tools directory has .c and .o files, but apparently only one executable, called 'tpm2'.

Does tpm2 now wrap the tools? Did something go wrong in the build? Will something change when I install?

--
Ken Goldman kgoldman(a)us.ibm.com
914-945-2415 (862-2415)




[-- Attachment #2: attachment.htm --]
[-- Type: text/html, Size: 2311 bytes --]

[tpm2] Re: building tpm tools - only built one tool?

[Imran Desai]

[-- Attachment #1: Type: text/plain, Size: 486 bytes --]

tpm2_tools and tss2_tools are now a busybox style commandlet. Ie
tpm2_getrandom becomes tpm2 getrandom. make install will install symlinks
to the old tool names and the tpm2 commandlet will interrogate argv[0] for
the command to run. This will provide backwards compatibility if they are
installed. If you wish to use the old names not installed system wide, set
DESTDIR during install to a separate path and set the proper directory on
PATH.

Thanks and regards,

Imran Desai