Generally it makes no sense as mingw32-make and win-make are the SAME binaries.The only difference in your case, is that you seem to put MinGW in PATH and try to invoke included GNU Make. Which can cause MinGW to be autodetected. Solution, as written in INSTALL: "Unpack it [mingw32-make] to your PATH or Harbour source root directory." (instead you put MinGW in PATH which happens to also contain mingw32-make) also: "It's recommended to make sure no tools in your PATH belonging to other C compilers are interfering with your setup." (in your case whole MinGW interferes with MSVC) plus: "You can also use included copy [of mingw-32make] named win-make.exe instead." 'clean' and 'install' are options described in the document, so I don't think they should be repeated in every make invocation examples. win-make is a convenience option, which may or may not be included in our distribution, so I don't want to include it in every example either. Solution is easy: put mingw32-make in your PATH, or create a separate dir for it and put that in your PATH. Overall, I'm giving up on giving "proper" instructions which is fine for everyone. This seems to become a "how to mess it up" / "how to misunderstand" / "how to pick nits" contest. It's hopeless. Everyone should get its act together and figure a little bit themselves. Brgds, Viktor
Ok, thanks for the responses. I understand your situation. I understood the procedure. Best regards, Itamar M. Lins Jr. _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
