Qt-interest Archive, May 2008
Building 4.4 apps with VS2005 SP1
Message 1 in thread
Hi Everybody,
Since swapping to 4.4, when I start Visual Studio (which is set to auto reload my last project), and press build, it fails like this:
------ Build started: Project: Test, Configuration: Debug Win32 ------
Linking...
LINK : fatal error LNK1181: cannot open input file '\lib\qtmaind.lib'
Project : warning PRJ0018 : The following environment variables were not found:
$(QTDIR)
Build log was saved at "file://c:\rising_cpp\trunk\projects_test\webkit\debug\BuildLog.htm"
Test - 1 error(s), 0 warning(s)
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
Then I select menu / Qt / Load solution from .pro, recreate the project and build, everything is OK, and there are no problems for the rest of the day. I have 4.4.0 in my PATH and selected in menu / tools / options / Qt tab, and VSIntegration 1.4.0.
Is anyone else getting this behaviour? I suspect the integration is not initialising properly. This problem did not occur with Qt 4.3.4 and VSInteg 1.3.3.
Regards,
Tony Rietwyk.
--
[ signature omitted ]
Message 2 in thread
Hi Tony,
indeed it looks like the integration is not initializing properly. Can
you still reproduce the behavior? If so, could you provide me a step by
step description how to reproduce it?
Also, to verify that this is a initialization problem, what happens if
you trigger the initialization manually, e.g. when invoking the Qt
toolbox inside VS?
Setting a global QTDIR environment variable is not recommended and may
not even bring the desired results since the VS integration maintains
it's own QTDIR which can be different from a globally set one. Changing
the QTDIR in VS is done via the property browser when the currently
selected item is a Qt project (in the solution browser).
Kind regards,
Thomas
> Hi Everybody,
>
> Since swapping to 4.4, when I start Visual Studio (which is set to auto reload my last project), and press build, it fails like this:
>
>
> ------ Build started: Project: Test, Configuration: Debug Win32 ------
> Linking...
> LINK : fatal error LNK1181: cannot open input file '\lib\qtmaind.lib'
> Project : warning PRJ0018 : The following environment variables were not found:
> $(QTDIR)
> Build log was saved at "file://c:\rising_cpp\trunk\projects_test\webkit\debug\BuildLog.htm"
> Test - 1 error(s), 0 warning(s)
> ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
>
>
> Then I select menu / Qt / Load solution from .pro, recreate the project and build, everything is OK, and there are no problems for the rest of the day. I have 4.4.0 in my PATH and selected in menu / tools / options / Qt tab, and VSIntegration 1.4.0.
>
> Is anyone else getting this behaviour? I suspect the integration is not initialising properly. This problem did not occur with Qt 4.3.4 and VSInteg 1.3.3.
>
> Regards,
>
> Tony Rietwyk.
>
> --
> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with "unsubscribe" in the subject or the body.
> List archive and information: http://lists.trolltech.com/qt-interest/
>
>
--
[ signature omitted ]
Message 3 in thread
Thomas wrote on Friday, 16 May 2008 18:50
> Hi Tony,
>
> indeed it looks like the integration is not initializing
> properly. Can
> you still reproduce the behavior? If so, could you provide me
> a step by
> step description how to reproduce it?
>
> Also, to verify that this is a initialization problem, what
> happens if
> you trigger the initialization manually, e.g. when invoking the Qt
> toolbox inside VS?
>
> Setting a global QTDIR environment variable is not
> recommended and may
> not even bring the desired results since the VS integration maintains
> it's own QTDIR which can be different from a globally set
> one. Changing
> the QTDIR in VS is done via the property browser when the currently
> selected item is a Qt project (in the solution browser).
>
>
> Kind regards,
>
> Thomas
Hi Thomas,
Thank-you for responding.
I am using VS2005 version 8.0.50727.762 (SP.050727-7600), with .Net
framework version 2.0.50727 SP1. I am also using a plug-in called DPack
(v2.7.3) that does Delphi key-bindings and some other things. Prior to using
4.4, I was using VS2005 (not SP1) with VSInteg 1.3.3 and the same DPack
version without any problems.
The problem occurs after starting VS - both the first time after booting,
and subsequently after closing VS.
- Trying to do a build with an auto-opened project fails.
- Closing the project, then restarting VS, then opening the project and
building fails.
- Restarting VS with the auto-opened project, then double-clicking a form,
doing menu / Qt / Qt-Toolbox to display the toolbox, then trying to build
fails.
- Trying rebuild, deletes the intermediate files and then fails.
- Closing and reopening the project with the form still selected and the
toolbox visible, then building fails.
- Regenerating the project with the project open, then selecting 'Discard'
on the 'Conflicting File Modification Detected' popup, then building works.
- Restarting VS with the project closed, then regenerating the project
(which leaves the project open), then building works.
So it seems the only thing that helps is regenerating the project.
Let me know if there are any other combinations that you would like me to
try.
Tony Rietwyk
--
[ signature omitted ]
Message 4 in thread
Hi Tony,
this bug is already fixed and the fix will be part of the next
integration release. For now, you can workaround the problem by manually
assigning a Qt version to the project after importing it. You do that by
selecting the imported project in the solution explorer and then setting
a Qt version in the property browser. This has to be done only once.
Hope this helps!
Thomas
Tony Rietwyk wrote:
> Thomas wrote on Friday, 16 May 2008 18:50
>
>
>> Hi Tony,
>>
>> indeed it looks like the integration is not initializing
>> properly. Can
>> you still reproduce the behavior? If so, could you provide me
>> a step by
>> step description how to reproduce it?
>>
>> Also, to verify that this is a initialization problem, what
>> happens if
>> you trigger the initialization manually, e.g. when invoking the Qt
>> toolbox inside VS?
>>
>> Setting a global QTDIR environment variable is not
>> recommended and may
>> not even bring the desired results since the VS integration maintains
>> it's own QTDIR which can be different from a globally set
>> one. Changing
>> the QTDIR in VS is done via the property browser when the currently
>> selected item is a Qt project (in the solution browser).
>>
>>
>> Kind regards,
>>
>> Thomas
>>
>
> Hi Thomas,
>
> Thank-you for responding.
>
> I am using VS2005 version 8.0.50727.762 (SP.050727-7600), with .Net
> framework version 2.0.50727 SP1. I am also using a plug-in called DPack
> (v2.7.3) that does Delphi key-bindings and some other things. Prior to using
> 4.4, I was using VS2005 (not SP1) with VSInteg 1.3.3 and the same DPack
> version without any problems.
>
> The problem occurs after starting VS - both the first time after booting,
> and subsequently after closing VS.
>
> - Trying to do a build with an auto-opened project fails.
> - Closing the project, then restarting VS, then opening the project and
> building fails.
> - Restarting VS with the auto-opened project, then double-clicking a form,
> doing menu / Qt / Qt-Toolbox to display the toolbox, then trying to build
> fails.
> - Trying rebuild, deletes the intermediate files and then fails.
> - Closing and reopening the project with the form still selected and the
> toolbox visible, then building fails.
>
> - Regenerating the project with the project open, then selecting 'Discard'
> on the 'Conflicting File Modification Detected' popup, then building works.
> - Restarting VS with the project closed, then regenerating the project
> (which leaves the project open), then building works.
>
> So it seems the only thing that helps is regenerating the project.
>
> Let me know if there are any other combinations that you would like me to
> try.
>
> Tony Rietwyk
>
> --
> To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with "unsubscribe" in the subject or the body.
> List archive and information: http://lists.trolltech.com/qt-interest/
>
>
--
[ signature omitted ]
Message 5 in thread
It is working fine for me, however I set my QTDIR environment variable to
point to the 4.4.0 version directory. The error message below suggest that
you didn't set the QTDIR variable. I think you can do it at the system level
(System->Advanced->Environment Variables) or at the project level in
VS2005...
"Tony Rietwyk" <tony.rietwyk@xxxxxxxxxxxxxxxx> wrote in message
news:g0iovg$jqk$1@xxxxxxxxxxxxxxxx
Hi Everybody,
Since swapping to 4.4, when I start Visual Studio (which is set to auto
reload my last project), and press build, it fails like this:
------ Build started: Project: Test, Configuration: Debug Win32 ------
Linking...
LINK : fatal error LNK1181: cannot open input file '\lib\qtmaind.lib'
Project : warning PRJ0018 : The following environment variables were not
found:
$(QTDIR)
Build log was saved at
"file://c:\rising_cpp\trunk\projects_test\webkit\debug\BuildLog.htm"
Test - 1 error(s), 0 warning(s)
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
Then I select menu / Qt / Load solution from .pro, recreate the project and
build, everything is OK, and there are no problems for the rest of the day.
I have 4.4.0 in my PATH and selected in menu / tools / options / Qt tab, and
VSIntegration 1.4.0.
Is anyone else getting this behaviour? I suspect the integration is not
initialising properly. This problem did not occur with Qt 4.3.4 and VSInteg
1.3.3.
Regards,
Tony Rietwyk.
--
[ signature omitted ]
Message 6 in thread
"B.C." <bikerc@xxxxxxxxx> wrote in message
news:g0jani$mio$1@xxxxxxxxxxxxxxxx
> It is working fine for me, however I set my QTDIR environment variable to
> point to the 4.4.0 version directory. The error message below suggest that
> you didn't set the QTDIR variable. I think you can do it at the system
> level
> (System->Advanced->Environment Variables) or at the project level in
> VS2005...
Setting the QTDIR variable should not be necessary. The integration package
should take care of this internally. That's how you can switch between
different
Qt versions.
--
[ signature omitted ]
