On 5/15/12, MARTIN Pierre <[email protected]> wrote:
> Dear list,
>
> i'm trying to make a set of patches for the Qt Installer Framework.
> i have corrected most of the errors i have found (But will request
> a few advices later about the win32 API offering functionA and
> functionW based on the charset). Right now, the only thing i'm
> working on is linking.
>
> i have erradicated all problems except for one:
> kdsysinfo_win.cpp:-1: error: undefined reference to
> `WNetGetUniversalNameW@16'
> i have looked over various websites and as far as i understand,
> i should be linking against libmpr, what i have done. However,
> the problem persists, and i'm wondering if MinGW-w64 libs and
> headers could be somehow different than the ones used by the
> Qt IFW package developers.
>
> Is there at your knowledge any difference in such library, or more
> specifically a known problem with this WNetGetUniversalName
> function?
>
I do this:
$ cat 1.c
#define WIN32_LEAD_AND_MEAN
#include <windows.h>
#include <winnetwk.h>
int main () {
return WNetGetUniversalNameW(0,0,0,0);
}
$ /opt/cross_win32/bin/i686-w64-mingw32-gcc 1.c -lmpr
$ ls -l a.exe
-rwxrwxr-x 1 ozzie ozzie 108067 2012-05-15 18:14 a.exe
... seems to link fine. What is your command line?
> Thank you,
> Pierre.
>
--
O.S.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
