IMHO, having a fat library is bad idea because it doesn't seem to work well fur the last several years. Wasting space is another reason.
IMHO, you're better off recompiling once you get the new ARM-based Mac. Keep x86_64 stuff on Intel (don't drag it to ARM), and build ARM-only stuff on ARM. Or keep experimenting with fat libraries and fat binaries - but be prepared to experience pain. > On Oct 15, 2020, at 23:38, Tolu <tfapohu...@gmail.com> wrote: > > Thanks for the quick reply. > > I currently use Crypto++ in an application. The application is MacOS only. > Since Apple is switching to Arm-based MacOS machines, I need to support both > Intel and Arm CPUs. Essentially, I would need the Crypto++ built for x86_64 > and arm64 (if I want to run natively on the host machine). I do not know all > the intricacies of Crypto++. Could you please elaborate on why having > building Crypto++ as a universal (fat) library is a bad idea? > > Thanks >> On Wednesday, October 14, 2020 at 11:30:59 PM UTC-4 Mouse wrote: >> I have never built Crypto++ as a universal (fat) library, and personally >> think it's not a good idea. >> >> >>>> On Oct 14, 2020, at 20:39, Tolu <tfapo...@gmail.com> wrote: >>>> >>> Hello, >> >>> >>> I am trying to create a universal library (x86_64 and arm64), however, I am >>> difficulties building the cryptopp library on arm64 on MacOS. When I run >>> the `make -f GNUmakefile-cross` I get the following errors: >>> >>> integer.cpp:650:2: error: unknown token in expression >>> INTEL_NOPREFIX >>> ^ >>> ./cpu.h:46:25: note: expanded from macro 'INTEL_NOPREFIX' >>> #define INTEL_NOPREFIX ".intel_syntax;" >>> >>> >>> Has anyone successfully built the cryptopp on MacOS as a universal binary? >>> >>> Thanks in advance >> >>> -- >>> You received this message because you are subscribed to "Crypto++ Users". >>> More information about Crypto++ and this group is available at >>> http://www.cryptopp.com and >>> http://groups.google.com/forum/#!forum/cryptopp-users. >>> --- >>> 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 cryptopp-user...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/cryptopp-users/5e6e58a9-f361-4e86-904f-11d3d0980c2cn%40googlegroups.com. > > -- > You received this message because you are subscribed to "Crypto++ Users". > More information about Crypto++ and this group is available at > http://www.cryptopp.com and > http://groups.google.com/forum/#!forum/cryptopp-users. > --- > 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 cryptopp-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/cryptopp-users/bc6c4cc3-42be-4d2a-b720-96e81a4f8e89n%40googlegroups.com. -- You received this message because you are subscribed to "Crypto++ Users". More information about Crypto++ and this group is available at http://www.cryptopp.com and http://groups.google.com/forum/#!forum/cryptopp-users. --- 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 cryptopp-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/cryptopp-users/57AD01C5-ED48-43BC-B433-AEB40C43AAE7%40gmail.com.
smime.p7s
Description: S/MIME cryptographic signature
