I say we don't need to overcomplicate the build. We have way to many options and flags already. It is not good. We're losing simplicity,which was/is one of the endearing qualities of this project (at least build-wise).
On Thu, Jul 23, 2015 at 11:27 AM, Jeffrey Walton <[email protected]> wrote: > On Thu, Jul 23, 2015 at 11:04 AM, David Irvine > <[email protected]> wrote: > > Is it time to really consider cmake or similar as a build system. It is a > > bit more work, but does give the freedom for users to use gui config > tools > > etc. It is also more cross platform aware and will reproduce .sln for > > windows and apple xcode configs as well as makefiles. > > Yeah, we tried to get someone to provide a CmakeList.txt for those who > want to use it. There were no takers for the task. There were some > objections to it, so maybe it was just as well. > > At minimum, I feel like a CmakeList.txt should be available on the > patch page at http://www.cryptopp.com/wiki/Category:Patch. > > (I've had a fair amount of bad experiences with Autotools over the > years, and I would personally be opposed to Autotools. So I kind of > understand the objections to Cmake. If folks are opposed to one Cmake > file, what are they going to do with all the Autotools pollution?). > > Jeff > > > On Thu, Jul 23, 2015 at 2:45 PM, Jeffrey Walton <[email protected]> > wrote: > >> On Thursday, July 23, 2015 at 9:10:46 AM UTC-4, Mouse wrote: > >>> > >>> My biggest concern is that the build control becomes more and more > >>> complicated. I don't really like it, as it could (a) deprive "normal" > users > >>> from the ability to tweak it when needed, and (b) lay too heavy a > burden on > >>> the project maintainers... > >>> > >>> One sed script won't turn the tide. But if more sad scripts would > >>> come...? ;) > >> > >> Yeah, the thing I don't like is the makefile touching the configuration > >> file and touching defines the user may have modified. This is what I was > >> thinking with respect to sed... Break it out into two variables: > >> > >> // DFW (don't fiddle with)!!! The makefile sets this based on your build > >> tools and settings!!! > >> // #define CRYTPOPP_CLANG_ASSEMBLER_MK > >> > >> // Feel free to turn knobs on CRYTPOPP_CLANG_ASSEMBLER > >> #if defined(__clang__) && defined(CRYTPOPP_CLANG_ASSEMBLER_MK) > >> # define CRYTPOPP_CLANG_ASSEMBLER > >> #endif > >> > >> Then, in GNUmakefile: > >> > >> CLANG_ASSEMBLER ?= $(shell $(CXX) -xc -c /dev/null -Wa,-v -o/dev/null > 2>&1 > >> | $(EGREP) -i -c "^clang") > >> ifeq ($(CLANG_ASSEMBLER),0) > >> $(shell sed -i "s|^#define CRYTPOPP_CLANG_ASSEMBLER_MK|// #define > >> CRYTPOPP_CLANG_ASSEMBLER_MK|g" GNUmakefile) > >> else > >> $(shell sed -i "s|^// #define CRYTPOPP_CLANG_ASSEMBLER_MK|#define > >> CRYTPOPP_CLANG_ASSEMBLER_MK|g" GNUmakefile) > >> endif > >> > -- Regards, Mouse -- -- 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.
