How to use CreateFont API function in Qt5

kshegunov

@Uncle-Kris
LIBS += -L"H:\Windows Kits\8.1\Lib\winv6.3\um\x86/gdi32"\

This is incomplete. The backslash at the end means it continues on to the next line. Also, when giving paths, use the forward slash instead of the a backwards. It is recognized on windows and you'll work around a ton of problems with escaping in the long run.

There is no info on compiler dependency. Just folder full of libraries. How I can check?

It should be noted somewhere on the MS's site, however I have no windows on hand to check. What compiler are you using currently? The 8.1 SDK should work with MSVC 2012/2013 if I recall correctly.

SGaist

@kshegunov Not a typo ;) See here

kshegunov

@SGaist said:

It would rather be LIBS += -LGdi32.

I know, I know. Still looks like you typed -L instead of -l ;)

SGaist

Haaaaaaa that typo ! Good catch ! Then indeed, there was ! :)

Uncle Kris

@kshegunov There was a next line. I have removed it for test time. Also changes to shash/backslash do not make any difference for now. Linker is not happy.

Uncle Kris

@SGaist What typo? Can you be more specific, please? Compiler has no problem with that line. And it used to work in another IDE.

Also: "It would rather be LIBS += -LGdi32." No. Without full path there is a message that file is not found. -L and -l makes no difference so far.

kshegunov

@Uncle-Kris
A library is passed to qmake (respectively make) with the following syntax:

LIBS += -L/path/to/library -llibraryname

The typo was that @SGaist used the switch for library path -L to specify the library name. It should've been -lgdi32. So in your case it'd look something like this:

LIBS += -L"H:/Windows Kits/8.1/Lib/winv6.3/um/x86" -lgdi32

SGaist

Yes the typo was the L vs l but still the library name is Gdi32

kshegunov

@SGaist said:

but still the library name is Gdi32

The windows linker isn't case sensitive. :)

SGaist

@kshegunov said:

@SGaist said:

but still the library name is Gdi32

The windows linker isn't case sensitive. :)

Indeed, but I wouldn't be surprised if that changed at some point :D

kshegunov

@SGaist said:

Indeed, but I wouldn't be surprised if that changed at some point :D

Perhaps, perhaps. Although, judging from the time it took MS to introduce the x64 compiler, if it were to change, it'd take decades. And since it hasn't changed for over 30 years, I really doubt that it ever will. :D