LNK recurring error
(30/10/14 : Issue has been solved, fix: Set Windows Application Experience to 'manual' in Windows services)
Hi Qt Forums,
I'm having a recurring issue when running a program created in Qt Creator, the program runs fine at first, but if a change is made (it seems like changes to the header file) and try running it again I get a LNK error saying the file cannot be opened.
I looked online and this issue seems to occur when the programs already running, but the file isn't appearing in the task manager and the IDE says it's not running.
I have tried running qmake and cleaning the project but that doesn't seem to help, do you have any solutions for this? I'm using Qt 5.3 with MSVC12 64bit compiler
The error seems to go away after like 5 minutes... this isn't ideal.
Hi and welcome to devnet,
Got an antivirus running ?
[quote author="SGaist" date="1413667218"]Hi and welcome to devnet,
Got an antivirus running ?[/quote]
Yes I had Avast Antivirus running, I disabled it temporarily and the issue remains.
Ok, then i'd try to find what is locking that file. Maybe "this":http://technet.microsoft.com/en-us/sysinternals/bb896655.aspx might help
[quote author="SGaist" date="1413725165"]Ok, then i'd try to find what is locking that file. Maybe "this":http://technet.microsoft.com/en-us/sysinternals/bb896655.aspx might help[/quote]
I ran Handler and used the command handle -p address (.exe file is AddressBook) and during the time where the LNK error appeared no handles were shown.
Just to clarify, this issue happens when deleting a reference from a header file (in this case #include <QWidget>), saving the program, then undoing that deletion and saving again at which point the program takes around 2-3 minutes before it manages to compile again.
Doing that while the application is running ?
When running active handles are
!http://puu.sh/cnpWR/a8c0ae1cad.png(active handles addressbook.exe)!
That is probably completely unrelated but, can you try again after moving your project to a spaceless folder ?
Seems like I've solved the issue, I had to set Windows Application Experience to 'manual' in Windows services. Thanks for your help SGalst.