>>>>> On Thu, 23 Feb 2006 00:33:06 +0000 (UTC), Enrico Forestieri <[EMAIL 
>>>>> PROTECTED]> said:



Enrico> Stephen Harris <[EMAIL PROTECTED]> writes:

>> I did not succeed in compiling Qt. I got the files in the right

>> directory with cvs, but the ./configure failed quickly with the

>> error

>> 

>> make: *** [project.o] Error 1 qmake failed to build. Aborting



Enrico> Probably this is because the qt3/include dir should be

Enrico> populated first.  I had that dir already populated by a

Enrico> previous MinGW build, so I forgot to add the instructions to

Enrico> do so. I have updated the Qt patches and the howto at

Enrico> http://wiki.lyx.org/LyX/LyXOnCygwin

Enrico> -- Enrico



-----------------------------------------



SH: Ok, I will give it another try. I did notice an apparent

discrepancy in the instuctions from the LyXonCygwin page:



-----------------------------------------------------



In this howto all examples are shown for tcsh, but it is 

trivial to change them for bash. Mainly, it is simply a 

matter of substituting "export XXX=YYY" in place of 

"setenv XXX YYY" (or simply use tcsh instead of bash).

 

--------------------------------------------------



If your Qt source tree is not in /usr/local/src/qt3, you 

should now modify as appropriate the following line 



export QTDIR=/usr/local/src/qt3

at the very start of the following sh scripts: 

config.tests/unix/endian.test 

config.tests/unix/ipv6.test 

config.tests/unix/largefile.test 

config.tests/unix/ptrsize.test 

config.tests/unix/stl.test 

---------------------------------------------



SH: It appears to me that "export QTDIR=/usr/local/src/qt3"

is written in bash syntax rather than "all" tcsh syntax?

I did try the tcsh shell and I liked how it displayed the

contents (directory vs. file).



I have a Mingw directory of Qt3 from LyX140-pre3 already

but I will follow the instructions on the webpage as a

proof of concept (hope). I'm (un?)fortunately perfectionistic.



Supercitelfully yours,

Stephen  

Reply via email to