On 03/12/2018 09:48 PM, Mark Hatle wrote:
Then an advanced user to select a specific version of the 'alternatives'. The key with all of this is that it needs to be 'reasonable' for both the recipe maintainer and the end user. Having to manually rename things, use the existing update-alternatives, etc really isn't a good idea -- even if it solves (some of) the user issues.
But what is the specific need for having both 32 and 64 bit development packages *installed at the same time*? You do need to explain this, because any solution will add complexity and headaches for oe-core maintainers, and multilib is already far too complex and tricky.
If the customer is fine with switching between the two sets, then this can be trivially solved using existing tools:
1. Deinstall 32 bit dev packages on device. 2. Install matching 64 bit dev packages on device ... or vice versa. Just wrap it in a script. Alex -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
