Thanks to off-list help from Bill, I now have the following (subject
to mail wrapping issues) working with my build_projects project on
Wine:
bash.exe-3.1$ cmake -G"NMake Makefiles JOM"
-DCMAKE_C_COMPILER:FILEPATH=/z/home/wine/newstart/MinGW-4.7.2/bin/gcc.exe
-DCMAKE_RC_COMPILER:FILEPATH=/z/hom
On 2013-06-18 07:12-0400 Bill Hoffman wrote:
Try it without the --debug-trycompile, that might mess things up.
Good call. That made a big difference. Here is the "cmake.out" result from
bash.exe-3.1$ cmake -G"NMake Makefiles JOM" -DCMAKE_C_COMPILER=gcc ..
& cmake.out
CMake Warning at CM
On 6/10/2013 1:25 AM, Alan W. Irwin wrote:
Try commenting that out in Windows-GNU.cmake like this:
#enable_language(RC)
Then see if it works.
Hi Bill:
I was glad you could access the attachment from the list version. So I
am putting this discussion back on the list so you can continue to do
On 2013-06-10 10:58-0400 Bill Hoffman wrote:
The CMakeError.log you requested was not too informative:
bash.exe-3.1$ cat CMakeFiles/CMakeError.log
Determining if the C compiler works failed with the following output:
Next step is to try it by hand.
Start with a clean build tree and your
The CMakeError.log you requested was not too informative:
bash.exe-3.1$ cat CMakeFiles/CMakeError.log
Determining if the C compiler works failed with the following output:
Next step is to try it by hand.
Start with a clean build tree and your simple project. Then run
cmake with --debug-tr
On 2013-06-07 17:44-0400 Bill Hoffman wrote:
On 6/6/2013 9:44 PM, Alan W. Irwin wrote:
In this particular case I have specified gcc using
CMAKE_C_COMPILER. That bombs with the message
-- Check for working C compiler:
z:/home/wine/newstart/MinGW-4.7.2/bin/gcc.exe -- broken
Did you look in
On 6/6/2013 9:44 PM, Alan W. Irwin wrote:
In this particular case I have specified gcc using
CMAKE_C_COMPILER. That bombs with the message
-- Check for working C compiler: z:/home/wine/newstart/MinGW-4.7.2/bin/gcc.exe
-- broken
Did you look in the CMakeError.log file to see why it fails?
-
On 6/6/2013 9:44 PM, Alan W. Irwin wrote:
Assuming you confirm my finding that the "NMake Makefiles JOM" generator does
not currently work properly with the MinGW suite of compilers is
there some small change in language support that
would make that work?
I can confirm that I have never attempt
On 2013-06-06 20:11-0400 Bill Hoffman wrote:
On 6/6/2013 6:35 PM, Alan W. Irwin wrote:
http://releases.qt-project.org/jom/jom_1_0_13.zip). Are there known
problems with that jom release and how it interacts with Makefiles
produced by the "NMake Makefiles JOM" generator?
You could try building
On 2013-06-06 15:35-0700 Alan W. Irwin wrote:
I have just now tried the "NMake Makefiles JOM" generator for my
build_projects project, and I ran into a peculiar issue.
For example (from the "jom VERBOSE=1 build_ndiff" output) and with
single lines split up for e-mail purposes
Z:\home\wine\news
On 6/6/2013 6:35 PM, Alan W. Irwin wrote:
http://releases.qt-project.org/jom/jom_1_0_13.zip). Are there known
problems with that jom release and how it interacts with Makefiles
produced by the "NMake Makefiles JOM" generator?
You could try building cmake with your jom and running the regression
I have just now tried the "NMake Makefiles JOM" generator for my
build_projects project, and I ran into a peculiar issue.
For example (from the "jom VERBOSE=1 build_ndiff" output) and with
single lines split up for e-mail purposes
Z:\home\wine\newstart\cmake-2.8.10.2-win32-x86\bin\cmake.exe -E m
12 matches
Mail list logo
