Brad King wrote:
Brandon J. Van Every wrote:I explained the situation pretty clearly, I thought. E:\msys\1.0\bin\makefile does *NOT* run under a Windows command prompt. It's not supposed to. As I said before, there's a comment at the top of the binary that says it's not supposed to. Just to reiterate again in case there's any doubt: My test is plenty reliable. I have ***makeinfo***, not makeinfo.exe. Please read *ALL* the details of my post. There are ~30 tools in E:\msys\1.0\bin that do not have .exe suffixes, run fine under a MSYS shell, and are not intended to be run under anything but a MSYS shell. EXECUTE_PROCESS is finding a way to run them. My wild-assed-guess as to explanation, is that it execs arbitrarily named files, and does not check whether the filename is valid for a Windows command prompt. These MSYS tools are probably valid apps in some Windows-native sense, but not to a Windows command prompt. Anyway, if you want to test whether a program is executable under the build environment, you should use TRY_COMPILE with a small project with a custom command to run the program. That is a (tedious) workaround, but I still say the behavior of EXECUTE_PROCESS is bugged. I don't think anyone should have to write an OS-specific C coded exec wrapper just to determine if "makeinfo" actually works under the build environment. Cheers, Brandon Van Every |
_______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
