Qt-interest Archive, August 2007
4.3.0 installation failed if two comilers present
Message 1 in thread
I just downloaded 4.3.0 OpenSource and I am unable to compile it.
I have several compilers on my computer, usually I use MinGW and
c:\mingw\bin is a very first dir in PATH.
Configure.exe works fine and compile qmake with sole use of MinGW, but as
soon as qmake starts to generate makefiles it finds existence of Visual
Studio and does a mix of headers from GNU C and VC6. Of course compilation
of QT itself fails.
Is there a workaround for it?
Several compilers installed on the same computer was not a problem in
QT4.2.3.
--
[ signature omitted ]
Message 2 in thread
On 03.08.07 12:05:52, George Brink wrote:
> I just downloaded 4.3.0 OpenSource and I am unable to compile it.
> I have several compilers on my computer, usually I use MinGW and
> c:\mingw\bin is a very first dir in PATH.
> Configure.exe works fine and compile qmake with sole use of MinGW, but as
> soon as qmake starts to generate makefiles it finds existence of Visual
> Studio and does a mix of headers from GNU C and VC6. Of course compilation
> of QT itself fails.
> Is there a workaround for it?
> Several compilers installed on the same computer was not a problem in
> QT4.2.3.
You should report that as a Bug via Trolltechs bug reporting
channels.
Andreas
--
[ signature omitted ]
Message 3 in thread
George Brink wrote:
> I just downloaded 4.3.0 OpenSource and I am unable to compile it.
> I have several compilers on my computer, usually I use MinGW and
> c:\mingw\bin is a very first dir in PATH.
> Configure.exe works fine and compile qmake with sole use of MinGW, but as
> soon as qmake starts to generate makefiles it finds existence of Visual
> Studio and does a mix of headers from GNU C and VC6. Of course compilation
> of QT itself fails.
> Is there a workaround for it?
> Several compilers installed on the same computer was not a problem in
> QT4.2.3.
>
Yes, this was a change in behavior (configure.exe) in 4.3 where it
starts taking into account the LIB and INCLUDE environment variables for
MinGW. The solution is to remove Visual Studio specific paths from the
environment variables.
Girish
--
[ signature omitted ]
Message 4 in thread
Thanks. Remove LIB and INCLUDE from environment, do full reconfigure and QT
compiled. But is not a good solution. I still like to have LIB and INCLUDE
environment variables for VC6...
Can you do some switch in next version for configure/qmake to enable/disable
this behavior?
"Girish Ramakrishnan" <girish@xxxxxxxxxxxxx> wrote in message
news:f918va$334$1@xxxxxxxxxxxxxxxxxxxxx
> George Brink wrote:
> > I just downloaded 4.3.0 OpenSource and I am unable to compile it.
> > I have several compilers on my computer, usually I use MinGW and
> > c:\mingw\bin is a very first dir in PATH.
> > Configure.exe works fine and compile qmake with sole use of MinGW, but
as
> > soon as qmake starts to generate makefiles it finds existence of Visual
> > Studio and does a mix of headers from GNU C and VC6. Of course
compilation
> > of QT itself fails.
> > Is there a workaround for it?
> > Several compilers installed on the same computer was not a problem in
> > QT4.2.3.
> >
>
> Yes, this was a change in behavior (configure.exe) in 4.3 where it
> starts taking into account the LIB and INCLUDE environment variables for
> MinGW. The solution is to remove Visual Studio specific paths from the
> environment variables.
>
> Girish
--
[ signature omitted ]
Message 5 in thread
George Brink wrote:
> Thanks. Remove LIB and INCLUDE from environment, do full reconfigure and QT
> compiled. But is not a good solution. I still like to have LIB and INCLUDE
> environment variables for VC6...
> Can you do some switch in next version for configure/qmake to enable/disable
> this behavior?
>
This change was made because we had many people setting the LIB and
INCLUDE variables to point to libraries like OpenSSL and expected Qt to
automagically pick up paths from those variables. The side effect of the
change is that it reads in the VS libraries and include too :-|. I
assume you have a "Open 4.3 console" shortcut, so maybe you can put
unset the variables in that startup script?
We are open to changing this behavior if someone can suggest how we can
do this better.
Girish
--
[ signature omitted ]
Message 6 in thread
Von: Girish Ramakrishnan
> George Brink wrote:
> > Thanks. Remove LIB and INCLUDE from environment, do full reconfigure and
> QT
> > compiled. But is not a good solution. I still like to have LIB and
> INCLUDE
> > environment variables for VC6...
> > Can you do some switch in next version for configure/qmake to
> enable/disable
> > this behavior?
> >
>
> This change was made because we had many people setting the LIB and
> INCLUDE variables to point to libraries like OpenSSL and expected Qt to
> automagically pick up paths from those variables. The side effect of the
> change is that it reads in the VS libraries and include too :-|. I
> assume you have a "Open 4.3 console" shortcut, so maybe you can put
> unset the variables in that startup script?
>
> We are open to changing this behavior if someone can suggest how we can
> do this better.
>
I don't see a probem here - setting LIB and INCLUDE should be done by vsvars32/64.bat and not set globally. I've msvc 7.1, 8 and MinGW installed and did not encounter a single problem because of wrong LIB and INCLUDE env vars.
Christian
--
[ signature omitted ]
Message 7 in thread
"Christian Ehrlicher" <Ch.Ehrlicher@xxxxxx> wrote in message
news:20070807063025.48380@xxxxxxxxxx
> Von: Girish Ramakrishnan
> I don't see a probem here - setting LIB and INCLUDE should be done by
> vsvars32/64.bat and not set globally. I've msvc 7.1, 8 and MinGW installed
and did not
> encounter a single problem because of wrong LIB and INCLUDE env vars.
Envirnonment variables are not a problem with VC 7+. But they were set
globaly for VC6. And some people still use VC6.
--
[ signature omitted ]
Message 8 in thread
"Girish Ramakrishnan" <girish@xxxxxxxxxxxxx> wrote in message
news:f993bt$fdg$1@xxxxxxxxxxxxxxxxxxxxx
> George Brink wrote:
> > Thanks. Remove LIB and INCLUDE from environment, do full reconfigure and
QT
> > compiled. But is not a good solution. I still like to have LIB and
INCLUDE
> > environment variables for VC6...
> > Can you do some switch in next version for configure/qmake to
enable/disable
> > this behavior?
> >
>
> This change was made because we had many people setting the LIB and
> INCLUDE variables to point to libraries like OpenSSL and expected Qt to
> automagically pick up paths from those variables. The side effect of the
> change is that it reads in the VS libraries and include too :-|. I
> assume you have a "Open 4.3 console" shortcut, so maybe you can put
> unset the variables in that startup script?
Actualy, I do not have shortucts like that. I use a different approach: for
my projects I create 'make.bat' in main project directory which set all
neccessary environment variables and path for specific compiler, run
corresponding make (mingw32-make, nmake, wmake, etc), copy test data, run
application, run test cases, and so on...
So it is not a problem for me to deal with mix GNUC <-> VC6 since I know
what is the cause of such mix. I just did not expect it...
> We are open to changing this behavior if someone can suggest how we can
> do this better.
Well, for start, it would be nice to have a switch in configure and qmake to
use or ignore INCLUDE and LIB. It can be set to ignore for mingw users by
default. 'Configure' knows which complier it uses, doesn't it?
And it certanly would not hurt to mention usage of this environment
variables in INSTALL or README files :)
--
[ signature omitted ]
