Just to clarify, I am not talking about using cygwin make, where they completely disable using drive letters. I am just talking about using the standard make 3.82 source and build with cygwin gcc. All of my microsoft compiled code builds fine when using the resultant make.exe. I am not using the w32 directory at all, while it seems all other builds require it.
Eli Zaretskii wrote: > >> Date: Mon, 4 Jun 2012 07:49:25 -0700 (PDT) >> From: Stacy Leon <stac...@comcast.net> >> >> If I build make with cygwin gcc by running configure and make I get an >> exe >> that works and passes the -j option to sub-makes. What are the drawbacks >> to >> using this build method? > > If you need to use Make for invoking Cygwin tools, no drawbacks at > all. But if you need to invoke native Windows and MinGW tools, there > will be subtle incompatibilities. > > _______________________________________________ > Make-w32 mailing list > Make-w32@gnu.org > https://lists.gnu.org/mailman/listinfo/make-w32 > > -- View this message in context: http://old.nabble.com/Build-with-cygwin-gcc-tp33958406p33959056.html Sent from the Gnu - Make - W32 mailing list archive at Nabble.com. _______________________________________________ Make-w32 mailing list Make-w32@gnu.org https://lists.gnu.org/mailman/listinfo/make-w32
