[SoM] Packaging should automatically pick swift libraries for the output

[stephen-hawley]

Here is the original snippet:

https://gist.github.com/dalexsoto/e1878713a15b4091215dc50d720afa49

swift-stdlib-tool no longer runs properly because it tries to fork other tools and can't find them. Maybe this can be fixed with xcrun instead of running directly? Maybe we need our own tool? Either way, this needs to be addressed.

[rolfbjarne]

Can you show the actual errors from swift-stdlib-tool?

[stephen-hawley]

If the --strip-bitcode option is present, you get a vague error that bitcode exited abnormally (72).
If you remove that option, you get a more useful error of not being able to find the sign tool (also 72).
Both appear to be launched through an xcrun version (see here, assuming that this reflects what's in Xcode 9.2)

[chamons]

I started looking at this and got this far:

https://github.com/xamarin/maccore/tree/fix-SoM-piglatin

The biggest thing was the checked in sample didn't have an ios version at all, nor the build bits.

However, it's failing on device during AOT for reasons I don't understand yet. I'll try to look more this week but I'm checkpointing myself in case that doesn't happen and someone looks at this while i'm out.

[chamons]

I've isolated the remaining larger issue to one that does not require any SoM code and have asked for assistance while I try more ideas: https://github.com/chamons/filed-bug-test-cases/tree/master/framework_load_issue