On Thursday, December 3, 2015 at 7:53:58 PM UTC-5, jh...@emocha.com wrote: > > My only comment would be that given a "complete" "mobile" configuration > (Android AND iOS) that there be some generic mobile target that would > package the lib* files appropriately to avoid them all overwriting > libcryptopp.a. And for that matter, the .o and exes should probably managed > as well, which gets me into potentially suggesting build directories. > Currently, you have to make clean when switching platforms. >
The common use case for folks using the library is to make in-place and then execute. If the object files and source files are not side-by-side, then configuring the debugger to match objects to sources becomes another task. That means we have complicated the task and have to field the questions. If you are trying to do this (as opposed to speaking hypothetically), then drive the Makefile through a script. Let the makefile make the targets, and then move the artifacts where you would like them. After each run, perform a 'make clean'. I do the same when building fat libraries on iOS. Crypto++ is safe for fat libraries, unlike, say, OpenSSL or cURL. Jeff -- -- 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.
