Add tss2-sys when generating bindings too

[ionut-arm]

The tss2-sys is only being linked to explicitly when the bindings are
not generated, after #226. This fixes that discrepancy.

Signed-off-by: Ionut Mihalcea [email protected]

[hug-dev]

In here maybe we should indicate every lib that we link to

[ionut-arm]

In here maybe we should indicate every lib that we link to

It's a bit problematic, because that field is made for one value, see doc. They say here there should be at most one package per links value, but I think it's the other way around as well.

[hug-dev]

Ah true, I think actually we discussed that in the post and said that maybe ideally there should be one -sys crate per lib. I guess this is fine to leave that for now.

[Superhepper]

Why is it only sys? Why is it not needed to link against each individual library in the software stack?

[ionut-arm]

Why is it only sys? Why is it not needed to link against each individual library in the software stack?

I'm not entirely sure, the problem only appeared when I tried to cross-compile Parsec - for some reason doing the same thing that we do in the cross-compilation tests for this crate doesn't work, it complains that the symbols in tss2-sys can't be found. I worry that if I ignore it and just link "by hand" to the library in the Parsec builds, every user of this crate might have to do the same for their binaries.