Gisle Vanem <[EMAIL PROTECTED]> writes: > If you adopt this style, I urge you to reconsider the "#undef > HAVE_OPENSSL" in config.h.
You're right; I never thought through the effect of the #undef lines on symbols defined via Makefile! configure-generated config.h has the undefs commented out, presumably to show that the default is "undefined", but without affecting Makefile-changed symbols. I'll now fix config.h. >> 5. Create windows/Makefile-$compiler for each $compiler we support, >> which contains the necessary CFLAGS, LDFLAGS, etc. configure.bat >> --$compiler would copy both windows/Makefile and >> windows/Makefile-$compiler to src. > > I think a single windows/makefile is enough. Instruct make to put > objects for each target into separate sub-dirs. Along the lines of: > > MSVC_OBJECTS = $(addprefix MSVC_obj/, $(SOURCE)) > MINGW_OBJECTS = $(addprefix MingW_obj/, $(SOURCE)) > > MSVC_obj/%.obj: %.c > cl -c $(MSVC_CFLAGS) -Fo$@ $< > > MingW_obj/%.obj: %.c > gcc -c $(MINGW_CFLAGS) -o $@ $< > > ------- > > And issuing "make -f ../windowsMakefile msvc" would AFAICS remove the > need for a configure.bat file Wouldn't you need to have separate targets for linking as well? And how would you handle the distinction between compilation flags, optimization flags, link flags, and so on?
