Having trouble adding User32.lib to project as linked library.

SGaist

Hi,

user32 is typically a lib that you shouldn't need to pass a path for. So I'd remove the -L option from your .pro file.

In any case, are you using a 32 or 64 bit Qt ? Whith which compiler ?

Crag_Hack

Thanks SGaist... using 32 bit QT Creator with Microsoft Visual C++ Compiler 14.0 (x86)

SGaist

It's the Qt version you use to build your application that is important, not the Qt Creator version.

Crag_Hack

Sorry ... QT is using MSVC 2013 32 bit according to QT Creator. I installed from the Windows online installer and checked both options for MSVC 2015 32 and 64 bit when installing.

Crag_Hack

So a little more background on the situation...

I switched from MinGW to MSVC2015 as my compiler in QT Creator. I am using QT Creator with Visual Studio 2015 Community to provide the compiler to QT Creator. With MinGW I had no problems. I am now getting this error message upon compile:

replicator.obj:-1: error: LNK2019: unresolved external symbol __imp__GetLastInputInfo@4 referenced in function "private: void __thiscall Replicator::idleBackup(void)" (?idleBackup@Replicator@@AAEXXZ

with code

void Replicator::idleBackup()
{
    LASTINPUTINFO time;

    time.cbSize = sizeof(time);
    GetLastInputInfo(&time);

    DWORD temp = GetTickCount() - time.dwTime;

Another person from a different site said this was because of the GetLastInputInfo dependency on User32.lib and that I needed to link that library.

SGaist

For which architecture are you building ?

Crag_Hack

You mean Windows right?

SGaist

No, I mean x86 vs x86_64

Crag_Hack

Or do you mean... x86/x64? In which case I'm doing x86 since the 64 bit QT Creator kit is broken.

hskoglund

Hi, I just tested on my Windows 10 with 32-bit MSVC2015, and to avoid that linker error you only have to add LIBS += -luser32 to your .pro file.

Crag_Hack

Something's up then cause I already tried that..

SGaist

Qt Creator is 32bit but that has no influence on the version of Qt you are using.

Crag_Hack

You're talking about my previous remark right? I mean the 64 bit MSVC build kit in QT Creator is broken. see here:
https://forum.qt.io/topic/72576/qt-creator-complaining-about-msvc-build-and-run-kit/3
D'oh the screenshot no longer works...I''l have to fix that

SGaist

Then also a silly question but, when you installed Visual Studio 2015, did you install the C++ stuff ? It's not selected by default.

Crag_Hack

I just did the default install, which didn't install the compilers; I knew because they didn't show up in QT Creator. I followed the instructions as here in comment 3 for question 1 in order to install the compilers. Do you think I need to install more C++ components?

SGaist

Did you check in Qt Creator that it detects the compilers ?

Crag_Hack

Yup:

alt text

SGaist

So that part is good. What about the Kits ?

Crag_Hack

Here 'tis... I am getting the error message from the compiler so it's obviously running. Just the library linking that's freaking out. I could pass verbose to the compiler to see if it gives more information.

alt text

SGaist

Then it looks like you are trying to setup a 32bit debugger on your 64bit Qt.