(resolved) adding versions of the libraries (was: Creator: size_t/ssize_t not recognized)

mzimmers

OK, I may have a new issue here. As noted above, I got this working with MinGW, which I'd installed into C:\Qt\4.8.3 per the installers recommendation. Today I was going to try to install the libraries for MSVC, and the installer wants to install into the same location as above. If I do this, I'm going to overwrite files and cause general confusion, right?

JKSH

Yep, installing into the same folder would do bad things :)

You can choose ANY new folder you want -- it won't affect Qt's ability to function. Even C:\PacMan\ will do, but I'd suggest something along the lines of C:\Qt\4.8.3_msvc\

P.S. And for consistency, the other installation could go into C:\Qt\4.8.3_mingw\ , but it's not necessary to disturb your private installation, if you can remember which is which

mzimmers

Yeah, that's what I figured. Since I already installed the MinGW version into \Qt\4.8.3, I guess I should remove this and re-install, huh?

Thanks.

JKSH

You're welcome. :) Whether you remove and reinstall or not is completely up to you -- Qt doesn't care. I would do it, because (1) I like a tidy and consistent computing environment, and (2) Qt Creator displays the name of your installation root in your "Qt Versions" list

Actually, point (2) made me realize something: It probably looks nicer to install into C:\Qt\4.8.3\mingw\ and C:\Qt\4.8.3\msvc2010\ instead of C:\Qt\4.8.3_mingw\ and C:\Qt\4.8.3_msvc\ ... because Qt Creator will then say

"Qt 4.8.3 (mingw)" and "Qt 4.8.3 (msvc2010)"
instead of
"Qt 4.8.3 (4.8.3_mingw)" and "Qt 4.8.3 (4.8.3_msvc)"

mzimmers

This is very useful; I think I'm almost there. Should I create a manual entry for the MSVC tool chain like I did for MinGW?

Edit:

I'm also getting some linker errors, stemming from my attempt to use sockets. According to the Microsoft online documentation, I should be including this library (which I am):

@_WIN32:libs += "C:/Program Files (x86)/Windows Kits/8.0/Lib/win8/um/x86/ws2_32.lib"@

Any idea what might be going on here?

JKSH

Pretty much.

I've always found manual setup easier than auto-detection, since I don't need to worry about the order of installation (the latter requires a library-and-then-Creator order). Also, I can remove/upgrade my manual installation at any time -- Creator will complain if an auto-detected library is removed, and won't auto-detect a version upgrade.

mzimmers

Thanks, JKSH. I got the libraries properly installed, and can build with MinGW. Trying to build with MSVC is giving me some problems that aren't Qt/Creator related, so I'm getting help in another forum for those.

More as it happens...

mzimmers

OK, I think I'm really close to wrapping this up. Here's the final (for now!) loose end:

MinGW and MSVC use different libraries for socket functions. MSVC uses ws2_32.lib, which I believe is the "standard" library for this purpose. MinGW, on the other hand, uses libws2_32.a.

So...how do I create entries in my .pro file that will work for both tool chains? (I assume that I want to use the different libraries for the respective tool chains.)

Thanks.

JKSH

Hmm... I'm not sure. Does the `-lws2_32' flag not work for both versions of the library?

It might be worth starting a new thread, to get a new set of eyes.

mzimmers

I wasn't familiar with that flag. How does one set linker flags within Creator? I tried using the QMAKE_LFLAGS option in my .pro file, but that didn't work (probably because it isn't a qmake flag).

Thanks.

JKSH

@
LIBS += -lws2_32
@

(although, I just realized it might be a GCC flag)

mzimmers

Ahh...I didn't realize that LIBS did double duty (specifying both libraries and flags). Excellent, and thanks for all the help.

JKSH

No problem :) Glad to hear that your setup has finally succeeded