I actually builds and runs when I target the iPhone :-| Can the cryptoPP headers files only be customised for a single architecture ( I have no experience with this ) ?
On Thursday, January 15, 2015 at 9:40:09 AM UTC+1, Jean-Pierre Münch wrote: > > Sorry, but I don't have any experience with cross-compiling. > > But I can make a good guess: > The amd64 architecture is not included as no iPhone has an AMD64 > processor. The other architectures are included as some iPhones use them. > Why it fails in the simulator then, I don't know. Can you try it out on an > iPhone? > > BR > > JPM > > Am Mittwoch, 14. Januar 2015 10:51:39 UTC+1 schrieb Andreas Kirkerud: >> >> Ok I see. >> >> Why would the compile script >> <https://github.com/diegostamigni/cryptopp-5.6.2-ios/blob/master/build-for-ios.sh> >> >> not include this architecture if it is needed ? >> >> Is the error message a sign that I have some incorrect properties in my >> xcode project's build settings ? >> >> >> >> On Tuesday, January 13, 2015 at 4:28:25 PM UTC+1, Jean-Pierre Münch wrote: >>> >>> Hey Andreas, >>> >>> I'm pretty sure that ARM64 IS NOT X86_64. >>> I do think that ARM64 is the 64-bit version of ARM. (or something >>> similar) >>> The reason is that you usually name things like X86_64 AMD64 (notice the >>> "D"?) which is something completely different than ARM. >>> For operationality you'll need to specify something like amd64. >>> Quote <https://wiki.debian.org/Arm64Port>: >>> >>> 'arm64' is the Debian port name for the 64-bit ARMv8 architecture, >>> referred to as 'aarch64' in upstream toolchains (GNU triplet >>> aarch64-linux-gnu) >>> >>> BR >>> >>> JPM >>> >>> Am Montag, 12. Januar 2015 19:55:58 UTC+1 schrieb Andreas Kirkerud: >>>> >>>> Yes that would perhaps be a reasonable cause, but once compiled, I >>>> check the cryptopp-lib for supported architectures using the lipo tool: >>>> >>>> $ lipo -info /path/to/lib/cryptopplib.a >>>> The output is: >>>> Architectures in the fat file: /path/to/lib/cryptopplib.a are: >>>> armv7 armv7s i386 arm64 >>>> >>>> From this I would guess that the arm64 arch covers the x86_64 :-s >>>> ... but the build error remains >>>> >>>> >>>> On Monday, January 12, 2015 at 5:06:55 PM UTC+1, Jean-Pierre Münch >>>> wrote: >>>>> >>>>> Hey, >>>>> >>>>> maybe it's just me and I'm too stupid of OS X (Windows fan). >>>>> BUT it looks like you didn't specifed AMD64 / X64 as target >>>>> architecture for the library build and hence you'll get an error when >>>>> trying to build something for AMD64 / X64. >>>>> >>>>> BR >>>>> >>>>> JPM >>>>> >>>>> Am Montag, 12. Januar 2015 12:19:37 UTC+1 schrieb Andreas Kirkerud: >>>>>> >>>>>> Hi, >>>>>> >>>>>> When building projects with the CryptoPP 5.6.2 lib ( added under >>>>>> "Link Binary With Libraries" and the header files pointed to under >>>>>> "Search >>>>>> Paths") in XCode I get the following error: >>>>>> >>>>>> Ld >>>>>> /Users/user/Library/Developer/Xcode/DerivedData/macarena-hgvjldavhkgvznzg/Build/Products/Debug-iphonesimulator/macarena.app/macarena >>>>>> >>>>>> normal x86_64 >>>>>> cd /Users/user/xcode/macarena >>>>>> export IPHONEOS_DEPLOYMENT_TARGET=8.1 >>>>>> export >>>>>> PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr >>>>>> >>>>>> ________________________________________________________________ >>>>>> >>>>>> Undefined symbols for architecture x86_64: >>>>>> "CryptoPP::AlignedAllocate(unsigned long)", referenced from: >>>>>> CryptoPP::AllocatorWithCleanup<unsigned char, >>>>>> true>::allocate(unsigned long, void const*) in SomeViewController.o >>>>>> "CryptoPP::AlignedDeallocate(void*)", referenced from: >>>>>> CryptoPP::AllocatorWithCleanup<unsigned char, >>>>>> true>::deallocate(void*, unsigned long) in SomeViewController.o >>>>>> ld: symbol(s) not found for architecture x86_64 >>>>>> clang: error: linker command failed with exit code 1 (use -v to see >>>>>> invocation) >>>>>> >>>>>> I get error when I include the following code in SomeViewController.mm >>>>>> : >>>>>> >>>>>> GCM<AES>::Encryption e; >>>>>> >>>>>> I have been able to use some other functions from the self compiled >>>>>> cryptopp-lib without it crashing on me, ex: >>>>>> >>>>>> CryptoPP::AutoSeededRandomPool randomRng(true, 32); >>>>>> >>>>>> >>>>>> I am trying to build for the simulator in XCode 6.1.1 running in Os X >>>>>> 10.10.1 (Yosemiti) on a MBP. >>>>>> >>>>>> >>>>>> The libs and headers have been compiled from ( I have tried some >>>>>> others as well with no luck): >>>>>> >>>>>> diegostamigni/cryptopp-5.6.2-ios >>>>>> <https://github.com/diegostamigni/cryptopp-5.6.2-ios> compiled in >>>>>> terminal ( Architectures in the fat file: armv7 armv7s i386 arm64) >>>>>> and >>>>>> kwongius/CryptoPP-iOS <https://github.com/kwongius/CryptoPP-iOS> patched >>>>>> with Cryptopp-mobile.zip >>>>>> <http://www.cryptopp.com/w/images/a/a0/Cryptopp-mobile.zip> >>>>>> compiling in XCode and terminal ( Architectures in the fat file: armv7 >>>>>> arm64) >>>>>> >>>>>> >>>>>> Tips on how to resolve this issue would be much appreciated :-) >>>>>> >>>>>> -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com. 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 cryptopp-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
