On 9/27/07, Dirk Colbry <[EMAIL PROTECTED]> wrote: > 1. Why didn't the MATLAB version of gmake work? My guess is that since the > MATLAB version of gmake is built for windows, it is having difficulty with > the cygwin directory structure.
Not sure about this one -- your guess sounds reasonable, though. The cygwin tools work well under cygwin, but maybe or maybe not so well when used directly from a windows cmd prompt. (Vice versa, too : windows tools work well under windows cmd prompt, but maybe not so well under a cygwin shell... many reasons for this... but the lesson is usually : use cygwin tools when in a cygwin shell, use other tools in other shells. :-) > 2. What is the difference between gmake and make? I Googled this one and > found that gmake stands for GNU make and it is basically the same as make > although different versions do exist and it can depend on the platform you > are using. > 3. The version of make in my install of cygwin is GNU Make 3.81 so why > didn't cygwin have links to both gmake and make? (this is obviously a > cygwin question and not a cmake question). I'm not sure about these two questions either. Cygwin does not appear to have a "gmake", unless it is buried inside some other package that is non-obvious simply from scanning through the list of available cygwin packages.... > 3. Why does cmake search for gmake before make? I am sure there is a > historical or logical reason for this, I just could not find it. I'm not sure what the reason behind it is (other than perhaps most Unix/Linux developers prefer gmake over make...?) but the implementation is clear from CMake's Modules/CMakeUnixFindMake.cmake : FIND_PROGRAM(CMAKE_MAKE_PROGRAM NAMES gmake make smake) MARK_AS_ADVANCED(CMAKE_MAKE_PROGRAM) Directing cmake to the right make with -D is a good solution for you if you want to keep your PATH set as it is... HTH, David _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
