[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-cygwin
Subject:    Re: cannot make QT_WIN32_2
From:       Holger Schroeder <holger-kde () holgis ! net>
Date:       2003-02-08 15:21:51
[Download RAW message or body]

well, as much as i understand it, every shell script has to start with
#!/bin/sh
or something, so that the shell can determine which shell it should feed 
this
script into. this is not the case in the current configure.cygwin. the other
point is that my checked out configure.cygwin has no execute rights.
i donīt know if cygwin handles that exactly the same way as linux, but a
program without x rights cannot be executed.

when you type . configure.cygwin the shell simply reads the file and
does the same as if you would copy and paste it line by line into a 
shell window.

this works fine for me, but the ./configure.cygwin does not work for me.

so for making it easier for other people to test this, ralf, could you 
change the
line in the compiling instructions, or are there any objections against 
this?

Holger

Ralf Habacker wrote:

>>Hi,
>>
>>i just tested compiling of a fresh cvs update again, it worked for me,
>>at least it was compiling
>>the moc stuff.
>>on the website there is written that you should type
>>./configure.cygwin
>>but for me it has to be
>>. configure.cygwin
>>(so you have to replace the slash (or backslash ?) by a space character)
>>
>>    
>>
>The difference between the two command are that the first on creates a subshell
>and the second not, instead is is run in the current shell, but this should make
>both.
>
>Ralf
>
>_______________________________________________
>kde-cygwin mailing list
>kde-cygwin@mail.kde.org
>http://mail.kde.org/mailman/listinfo/kde-cygwin
>
>  
>

_______________________________________________
kde-cygwin mailing list
kde-cygwin@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-cygwin
[prev in list] [next in list] [prev in thread] [next in thread]