Clean up codesigning and ensure signing success about adium

[estella144]

@Asher- Codesign is okay for me (Adium 1.5.10.4 on macOS 11.2.2).

[Asher-]

I'm not sure what you mean.

This issue concerns deployment of compiled sources to bundle a new Adium.app.

The problem is that the (very old) build scripts create the dylibs and then frameworkerize them without any code signing. When Xcode performs its copy phase and goes to sign the frameworks, it does so by signing the bundled /A file, expecting everything else to already be signed; instead, it finds that nothing is signed and bails.

Adium used to handle this by using --force --deep, but this is improper (and has been clarified as such by Apple more recently) and further did not work properly in all cases.

The proper solution is to codesign the dylibs as they are generated. This is not of itself difficult, but it requires the build scripts to be in working order— which they were not. They are now in mostly working order, with a few further details to be resolved, at which point codesigning can be easily integrated.

The only detail that I am not sure of offhand is how to use Xcode's automatic signing selection from the build script. I'm hoping Google knows.

[estella144]

@Asher- What I am saying is that the disk image should sign properly on my computer.

[Asher-]

This concerns signing of the binary, before any disk image is created.

[estella144]

@Asher- I have no binary, only dmg.

[Asher-]

Please don't comment on issues you don't understand unless it is to ask pertinent questions that lead to an understanding.

[estella144]

How do you know I don't understand this?

[Asher-]

If you understood this, you would be able to identify the evidence yourself.

[estella144]

@Asher- I don't have the binary to identify the evidence.