On 02/23/2012 10:55 PM, Bill Hoffman wrote:
On 2/23/2012 6:20 AM, Andrea Crotti wrote:
I don't think anyone really addressed your question. Your question
seems to have taken on a whole new life
The problem seems to be that your cmake file is creating makefiles
that use a python
On 2/24/2012 5:25 AM, Andrea Crotti wrote:
Ideally yes, unfortunately it's not really possible to avoid the python
call, without rewriting a lot of code in CMake/C (which is not a good
idea).
I will check what is the requirement, if the MinGW make is fine then
I'll just use that otherwise
I have MinGW installed in my system and today I added the bin directory
to the path, so I was able to
run all the commands also from a standard shell.
But now CMake complains:
CMake Error at c:/Program Files/CMake
2.8/share/cmake-2.8/Modules/CMakeMinGWFindMake.cmake:20 (MESSAGE):
sh.exe
On 2/23/2012 2:12 PM, Kenneth Boyd wrote:
On 2/23/2012 5:20 AM, Andrea Crotti wrote:
I have MinGW installed in my system and today I added the bin
directory to the path, so I was able to
run all the commands also from a standard shell.
But now CMake complains:
CMake Error at c:/Program
On Thu, Feb 23, 2012 at 2:46 PM, Bill Hoffman bill.hoff...@kitware.com wrote:
On 2/23/2012 2:12 PM, Kenneth Boyd wrote:
On 2/23/2012 5:20 AM, Andrea Crotti wrote:
I have MinGW installed in my system and today I added the bin
directory to the path, so I was able to
run all the commands also
On 2/23/2012 1:46 PM, Bill Hoffman wrote:
gmake behaves differently if /bin/sh is in the PATH. The makefiles
for MinGW Makefiles are written for gmake running in the mode where it
does not have /bin/sh. The makefiles for Msys Makefiles are written
so that they work with /bin/sh mode of
On 2/23/2012 2:40 PM, Kenneth Boyd wrote:
On 2/23/2012 1:46 PM, Bill Hoffman wrote:
A patch that found different make.exe or make-mingw and then tested
them would not be rejected. I still don't see how we can avoid
having separate generators for MinGW and Msys, and I certainly don't
think a
On 2/23/2012 3:40 PM, Kenneth Boyd wrote:
On 2/23/2012 1:46 PM, Bill Hoffman wrote:
Right. Unfortunately, I have MingW installed from official tarballs,
rather than the MSYS executable installer; the MSYS installer *.exe
critically failed for me back in 2001, so once I got a working install
On 2012-02-23 14:40-0600 Kenneth Boyd wrote:
On 2/23/2012 1:46 PM, Bill Hoffman wrote:
gmake behaves differently if /bin/sh is in the PATH. The makefiles for
MinGW Makefiles are written for gmake running in the mode where it does not
have /bin/sh. The makefiles for Msys Makefiles are
On 2012-02-23 16:02-0500 Bill Hoffman wrote:
Seems to me there are
only two [MinGW/MSYS] cases regardless of how it was installed:
1. you have /bin/sh in your PATH and gmake runs commands via /bin/sh
2. you do not have /bin/sh in your PATH and gmake runs commands via the
native windows
On 2/23/2012 5:18 PM, Alan W. Irwin wrote:
make commands. One is called MinGW/bin/mingw32-make.exe and is used
by the MinGW Makefiles generator while the other is called
MinGW/msys/1.0/bin/make.exe and is used by the MSYS Makefiles
generator. I presume those two executables correspond to
On 2/23/2012 3:02 PM, Bill Hoffman wrote:
On 2/23/2012 3:40 PM, Kenneth Boyd wrote:
On 2/23/2012 1:46 PM, Bill Hoffman wrote:
Right. Unfortunately, I have MingW installed from official tarballs,
rather than the MSYS executable installer; the MSYS installer *.exe
critically failed for me back
On 2/23/2012 6:20 AM, Andrea Crotti wrote:
So well I thought I could just use the MSYS Makefiles instead, but
reconfiguring and with the same target that doesn't work:
Scanning dependencies of target cleanup_system
process_begin: CreateProcess(NULL, /c/python25/python.exe
On 2/23/2012 3:50 PM, Alan W. Irwin wrote:
Both the MSYS Makefiles and MinGW Makefiles generators have worked
for me for a fairly recent version (20110802) of MinGW + MSYS
installed with the automatic installer. For the latter case I renamed
sh.exe to something else to keep sh.exe off the PATH.
On 2/23/2012 4:55 PM, Bill Hoffman wrote:
On 2/23/2012 6:20 AM, Andrea Crotti wrote:
So well I thought I could just use the MSYS Makefiles instead, but
reconfiguring and with the same target that doesn't work:
Scanning dependencies of target cleanup_system
process_begin: CreateProcess(NULL,
15 matches
Mail list logo
