* David Byron wrote on Sun, Aug 01, 2010 at 07:25:16PM CEST: > On Saturday, July 31, 2010, Ralf Wildenhues wrote: > > OK, so what if they are not actually running configure (or > > would not actually need to)? Presumably automake could > > produce a ready nmake file (or forbid, a vcproj) in at > > least simple cases? > > I could use some more info on how this would work in practice. Does this > mean that tarballs of packaged source contain an nmake file in addition to > configure and Makefile.in? I don't think it's safe to assume that one nmake > file is sufficient for all MSVC tool + Platform SDK versions. > > Plus also, if end users don't run configure they lose the ability to pass > args to configure (either --with-* or environment variable definitions).
Sure. I have no idea yet how exactly this could work in practice. I don't know these tools yet. I'm just throwing out these ideas to see if somebody has good input. In such a project, is there any scripting besides CMD that one could rely on? Thanks! Ralf
