RE: MSYS Makefiles Generator

2006-04-04 Thread Paulo Jorge Guedes
 -Original Message-
 From: William A. Hoffman [mailto:[EMAIL PROTECTED]
 Sent: segunda-feira, 3 de Abril de 2006 21:22
 To: kde-buildsystem@kde.org
 Subject: RE: MSYS Makefiles Generator
 
 At 02:46 PM 4/3/2006, Paulo Jorge Guedes wrote:
  -Original Message-
  From: William A. Hoffman [mailto:[EMAIL PROTECTED]
  Sent: segunda-feira, 3 de Abril de 2006 18:52
  To: kde-buildsystem@kde.org
  Subject: Re: MSYS Makefiles Generator
 
  There may be some cmake variables that can be converted to unix
paths
  that will fix the problem.  This looks like it may have to do with
the
  FindQt4.cmake changes.   What version of that are you using?
 
 I have committed a fix to cvs cmake that should fix the problem.

It seems it didn't :(

I also have a error: `getuid' undeclared; this is declared in the
kdewin32 include files. I changed my CMAKE_INCLUDE_PATH to:

$ echo $CMAKE_INCLUDE_PATH 
C:/Program Files/kdewin32/include/mingw;C:/Program
Files/kdewin32/include;D:/gnuwin32/include

But I still get the error. What am I doing wrong?

Paulo
___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem


Re: MSYS Makefiles Generator

2006-04-04 Thread Brad King
Paulo Jorge Guedes wrote:
-Original Message-
From: William A. Hoffman [mailto:[EMAIL PROTECTED]
Sent: segunda-feira, 3 de Abril de 2006 21:22
To: kde-buildsystem@kde.org
Subject: RE: MSYS Makefiles Generator

At 02:46 PM 4/3/2006, Paulo Jorge Guedes wrote:

-Original Message-
From: William A. Hoffman [mailto:[EMAIL PROTECTED]
Sent: segunda-feira, 3 de Abril de 2006 18:52
To: kde-buildsystem@kde.org
Subject: Re: MSYS Makefiles Generator

There may be some cmake variables that can be converted to unix
 
 paths
 
that will fix the problem.  This looks like it may have to do with
 
 the
 
FindQt4.cmake changes.   What version of that are you using?

I have committed a fix to cvs cmake that should fix the problem.
 
 
 It seems it didn't :(
 
 I also have a error: `getuid' undeclared; this is declared in the
 kdewin32 include files. I changed my CMAKE_INCLUDE_PATH to:
 
 $ echo $CMAKE_INCLUDE_PATH 
 C:/Program Files/kdewin32/include/mingw;C:/Program
 Files/kdewin32/include;D:/gnuwin32/include
 
 But I still get the error. What am I doing wrong?

Did you try this in a fresh build tree?  It may be that the 
CMakeDirectoryInformation.cmake files are left with the buggy version 
and prevent the fixed version from running and rewriting them.

-Brad
___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem


RE: MSYS Makefiles Generator

2006-04-04 Thread Paulo Jorge Guedes
 -Original Message-
 From: William A. Hoffman [mailto:[EMAIL PROTECTED]
 Sent: terça-feira, 4 de Abril de 2006 14:16
 To: kde-buildsystem@kde.org
 Subject: RE: MSYS Makefiles Generator
 
 At 05:39 AM 4/4/2006, Paulo Jorge Guedes wrote:
  -Original Message-
  From: William A. Hoffman [mailto:[EMAIL PROTECTED]
  Sent: segunda-feira, 3 de Abril de 2006 21:22
  To: kde-buildsystem@kde.org
  Subject: RE: MSYS Makefiles Generator
 
  At 02:46 PM 4/3/2006, Paulo Jorge Guedes wrote:
   -Original Message-
   From: William A. Hoffman [mailto:[EMAIL PROTECTED]
   Sent: segunda-feira, 3 de Abril de 2006 18:52
   To: kde-buildsystem@kde.org
   Subject: Re: MSYS Makefiles Generator
  
   There may be some cmake variables that can be converted to unix
 paths
   that will fix the problem.  This looks like it may have to do with
 the
   FindQt4.cmake changes.   What version of that are you using?
 
  I have committed a fix to cvs cmake that should fix the problem.
 
 It seems it didn't :(
 
 The dashboard is using a cmake from 3/17/2006 and that does not have the
 changes I commited.  You can see the version used by clicking on the icon
 that looks like a gear next to the note icon.  Your build is
 mojo.risin.mingw right?

Right.

Sorry for didn't mention before but I'm not testing with the dashboard. It's a 
fresh updated checkout that I use to see if the problem is with the dash setup 
or not.

 I also have a error: `getuid' undeclared; this is declared in the
 kdewin32 include files. I changed my CMAKE_INCLUDE_PATH to:
 
 $ echo $CMAKE_INCLUDE_PATH
 C:/Program Files/kdewin32/include/mingw;C:/Program
 Files/kdewin32/include;D:/gnuwin32/include
 
 But I still get the error. What am I doing wrong?
 
 Maybe rebuild kdewin32, reinstall it, and then remove CMakeCache.txt
 from the build tree.   

Yeah, I did that (see above) but didn't work.

 Part of the nightly build process should be
 a separate build of kdewin32 and install.  (did I mention that this
 is not a good way to do this :) ).

kdewin32 installs on C:/Program Files/kdewin32.
My envs are set like this:

CMAKE_INCLUDE_PATH
C:/Program Files/kdewin32/include/mingw;C:/Program 
Files/kdewin32/include;D:/gnuwin32/include

CMAKE_LIBRARY_PATH
C:/Program Files/kdewin32/lib; C:/Program Files/kdewin32/bin;D:/gnuwin32/lib

This used to work. Don't know what the problem is.

I though this was a specific problem with my dashboard setup but I got the same 
errors with a free build.

Paulo

___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem


RE: MSYS Makefiles Generator

2006-04-04 Thread William A. Hoffman
At 10:56 AM 4/4/2006, Paulo Jorge Guedes wrote:
Right.

Sorry for didn't mention before but I'm not testing with the dashboard. It's a 
fresh updated checkout that I use to see if the problem is with the dash setup 
or not.

Make sure you start from an empty build tree.

-Bill

___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem


RE: MSYS Makefiles Generator

2006-04-04 Thread Paulo Jorge Guedes
 -Original Message-
 From: Brad King [mailto:[EMAIL PROTECTED]
 Sent: terça-feira, 4 de Abril de 2006 14:37
 To: kde-buildsystem@kde.org
 Subject: Re: MSYS Makefiles Generator
 
 Did you try this in a fresh build tree?  It may be that the
 CMakeDirectoryInformation.cmake files are left with the buggy version
 and prevent the fixed version from running and rewriting them.

Yes. Same error:

d:/kde/kdewin32-build/CMakeFiles/CMakeDirectoryInformation.cmake:13:
syntax error, unexpected cal_ERROR, expecting $end (4), when parsing string 
D:\downloads\qt-win-opensource-src-4.1.1\mkspecs/default
CMake Error: Target DependInfo.cmake file not found
CMake Error: Directory Information file not found

Paulo
___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem


RE: MSYS Makefiles Generator

2006-04-04 Thread Paulo Jorge Guedes
 -Original Message-
 From: Paulo Jorge Guedes [mailto:[EMAIL PROTECTED]
 Sent: terça-feira, 4 de Abril de 2006 16:28
 To: kde-buildsystem@kde.org
 Subject: RE: MSYS Makefiles Generator
 
  -Original Message-
  From: Brad King [mailto:[EMAIL PROTECTED]
  Sent: terça-feira, 4 de Abril de 2006 14:37
  To: kde-buildsystem@kde.org
  Subject: Re: MSYS Makefiles Generator
 
  Did you try this in a fresh build tree?  It may be that the
  CMakeDirectoryInformation.cmake files are left with the buggy version
  and prevent the fixed version from running and rewriting them.
 
 Yes. Same error:
 
 d:/kde/kdewin32-build/CMakeFiles/CMakeDirectoryInformation.cmake:13:
 syntax error, unexpected cal_ERROR, expecting $end (4), when parsing
 string D:\downloads\qt-win-opensource-src-4.1.1\mkspecs/default
 CMake Error: Target DependInfo.cmake file not found
 CMake Error: Directory Information file not found

Well, I renamed gnu32 and mingw unistd.h files and now it looks for the right 
unistd.h which has getuid() and friends declared. It seems that 
CMAKE_INCLUDE_PATH is ignored...

However, I get an error when including this file:

24: #include ../include/unistd.h

This include doesn't exist.

Paulo

___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem


RE: MSYS Makefiles Generator

2006-04-04 Thread William A. Hoffman
At 12:01 PM 4/4/2006, Paulo Jorge Guedes wrote:
Well, I renamed gnu32 and mingw unistd.h files and now it looks for the right 
unistd.h which has getuid() and friends declared. It seems that 
CMAKE_INCLUDE_PATH is ignored...

CMAKE_INCLUDE_PATH is used to find header files.  It does not add an actual -I 
to
the build.   

-Bill

___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem


Re: MSYS Makefiles Generator

2006-04-04 Thread Christian Ehrlicher
Paulo Jorge Guedes schrieb:
 -Original Message-
 From: William A. Hoffman [mailto:[EMAIL PROTECTED]
 Sent: terça-feira, 4 de Abril de 2006 17:09
 To: kde-buildsystem@kde.org
 Subject: RE: MSYS Makefiles Generator

 At 12:01 PM 4/4/2006, Paulo Jorge Guedes wrote:
 
 Well, I renamed gnu32 and mingw unistd.h files and now it looks for the
   
 right unistd.h which has getuid() and friends declared. It seems that
 CMAKE_INCLUDE_PATH is ignored...

 CMAKE_INCLUDE_PATH is used to find header files.  It does not add an
 actual -I to
 the build.
 

 I'm a little confused.

 The right unistd.h is in  C:\Program Files\kdewin32\include\mingw. That 
 file includes a  ../include/unistd.h that doesn't exist.

 The order of include paths should be set by me? I haven't had this problem 
 before, don't know what caused it and if it should be corrected on my side or 
 not (the missing  ../include/unistd.h seems like a real problem).

   
The unistd.h you're searching for is in your programm dir/MinGW/include

Christian
___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem


RE: MSYS Makefiles Generator

2006-04-04 Thread William A. Hoffman
At 11:28 AM 4/4/2006, Paulo Jorge Guedes wrote:
 -Original Message-
 From: Brad King [mailto:[EMAIL PROTECTED]
 Sent: terça-feira, 4 de Abril de 2006 14:37
 To: kde-buildsystem@kde.org
 Subject: Re: MSYS Makefiles Generator
 
 Did you try this in a fresh build tree?  It may be that the
 CMakeDirectoryInformation.cmake files are left with the buggy version
 and prevent the fixed version from running and rewriting them.

Yes. Same error:

d:/kde/kdewin32-build/CMakeFiles/CMakeDirectoryInformation.cmake:13:
syntax error, unexpected cal_ERROR, expecting $end (4), when parsing string 
D:\downloads\qt-win-opensource-src-4.1.1\mkspecs/default
CMake Error: Target DependInfo.cmake file not found
CMake Error: Directory Information file not found

OK, so I fixed this in CVS CMake.  However, it can fix it in kde with this
change:

In FindQt4.cmake:  (convert the path for mkspecs to unix style path)

   IF (NOT QT_MKSPECS_DIR)
EXEC_PROGRAM( ${QT_QMAKE_EXECUTABLE}
  ARGS -query QMAKE_MKSPECS
  OUTPUT_VARIABLE qt_mkspecs_dir )
# convert the path to unix style path
STRING(REGEX REPLACE  / qt_mkspecs_dir ${qt_mkspecs_dir})
SET(QT_MKSPECS_DIR ${qt_mkspecs_dir} CACHE PATH The location of the Qt 
mkspecs)
  ENDIF (NOT QT_MKSPECS_DIR)

The fix in cmake allows include directories to be windows style, and converts
them automatically in the include_directories command.

-Bill

___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem


Re: MSYS Makefiles Generator

2006-04-03 Thread Christian Ehrlicher
William A. Hoffman schrieb:
 At 01:29 PM 4/3/2006, Paulo Jorge Guedes wrote:
   
 Hi, 

 It seems that CMakeDirectoryInformation.cmake files are not being
 correctly generated. Notice the path on the mkspecs entry:

 [...]
 D:/downloads/qt-win-opensource-src-4.1.1/include/Qt
 D:\downloads\qt-win-opensource-src-4.1.1\mkspecs/default
 D:/downloads/qt-win-opensource-src-4.1.1/include/QtCore
 [...]

 I cannot say for sure but it seems to happen always on the mkspecs
 entry.

 Can I make anything on my side to fix this?
 

 I noticed that on the dashboard.   Can you send me your CMakeCache.txt file?
 There may be some cmake variables that can be converted to unix paths
 that will fix the problem.  This looks like it may have to do with the
 FindQt4.cmake changes.   What version of that are you using?

 (I will work on the generation of the directory information file so that
 it will not have incorrect paths in it.)
   
I introduced QT_MKSPECS because I thought I need qplatformdefs.h. But I 
did it the way like all the other vars are generated...

Christian
___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://mail.kde.org/mailman/listinfo/kde-buildsystem