> With Apple's new requirements coming up to submit apps with bitcode > enabled, I am facing an issue while using crypto app compiled library in > our workspace as it is not bitcode enabled. > > Any steps or a place where I can figure out who to make cryptopp bitcode > enabled? >
Well, we probably won't support bitcode. We don''t want Apple rewriting our binaries and then pushing the bugs on us. If Apple fielded the bugs then I'd be happy to work with them on the support, but I doubt that will happen. In the meantime, and as a start, add -DCRYPTOPP_DISABLE_ASM and/or -DNO_OS_DEPENDENCE to your CXXFLAGS. I don't know what will happen after that, but that is where I would start. We added some bitcode support to the makefile in the past, but all it turned out to be as removing the temporary files (*.bc, IIRC). The XCode compilers I have access to were not capable of bitcode, so the investigation stalled. If you can provide SSH remote access to a well configured OS X machine (i.e., capable of bitcode), then I'd be happy to look at it with you. Jeff -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
