building kde3support on win32 cannot link
Hello, I am compiling kde3support on win32 in MSVC 8 2005. When linking skde3support linker shows the following errors: k3shortcutmenu.obj : error LNK2019: unresolved external symbol __declspec(dllimport) private: class QMenu __thiscall QMenu::operator=(class QMenu const ) (__imp_??4QMenu@@[EMAIL PROTECTED]@@Z) referenced in function public: class K3ShortcutMenu __thiscall K3ShortcutMenu::operator=(class K3ShortcutMenu const ) (??4K3ShortcutMenu@@[EMAIL PROTECTED]@@Z) k3dockwidget.obj : error LNK2001: unresolved external symbol __declspec(dllimport) private: class QMenu __thiscall QMenu::operator=(class QMenu const ) (__imp_??4QMenu@@[EMAIL PROTECTED]@@Z) k3popupmenu.obj : error LNK2001: unresolved external symbol __declspec(dllimport) private: class QMenu __thiscall QMenu::operator=(class QMenu const ) (__imp_??4QMenu@@[EMAIL PROTECTED]@@Z) k3shortcutmenu.obj : error LNK2019: unresolved external symbol __declspec(dllimport) private: __thiscall QMenu::QMenu(class QMenu const ) (__imp_??0QMenu@@[EMAIL PROTECTED]@@Z) referenced in function public: __thiscall K3ShortcutMenu::K3ShortcutMenu(class K3ShortcutMenu const ) (??0K3ShortcutMenu@@[EMAIL PROTECTED]@@Z) k3dockwidget.obj : error LNK2001: unresolved external symbol __declspec(dllimport) private: __thiscall QMenu::QMenu(class QMenu const ) (__imp_??0QMenu@@[EMAIL PROTECTED]@@Z) k3popupmenu.obj : error LNK2001: unresolved external symbol __declspec(dllimport) private: __thiscall QMenu::QMenu(class QMenu const ) (__imp_??0QMenu@@[EMAIL PROTECTED]@@Z) C:\kdelibs4\kdelibs\bin\Release\kde3support.dll : fatal error LNK1120: 2 unresolved externals What is wrong? What must I do to correct the error? Regards, Rikardo Tinauer -- ___ Rikardo Tinauer EBA, Agencija za elektronsko poslovanje d.o.o. Teslova ulica 30 SI-1000 Ljubljana e-mail: [EMAIL PROTECTED] internet: www.eba.si GSM: +386 031 382 379 TEL: +386 (0)1 477 66 01 __ ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: building kde3support on win32 cannot link
Hello, I am compiling kde3support on win32 in MSVC 8 2005. When linking skde3support linker shows the following errors: snip What is wrong? What must I do to correct the error? Imho it works fine for me (don't know excatly since I don't recompile this lib very often). - do you use Qt4.1.1? - is your svn up to date? - did you try to recompile the two files the error come from? - did you try to resolve the problem (since you want to compile kdelibs4 I assume that you want to help us with kde4) It looks like your builddir == srcdir: C:\kdelibs4\kdelibs\bin\Release\kde3support.dll This isn't a good idea (and I don't know excatly if cmake supports this). Christian btw: what has this problem todo with the buildsystem? -- Feel free mit GMX FreeMail! Monat für Monat 10 FreeSMS inklusive! http://www.gmx.net ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: building kde3support on win32 cannot link
Von: Rikardo Tinauer [EMAIL PROTECTED] Hello, * I am using the commercial version of Qt for win32, version 4.1.1. * I believe my svn is up to date, I downloaded files 2 days ago. * Yes I tried to recompile the files I tried reslovnig the problem. I found out that my Qt is built so it doesn't include the symbols for the operator and copy constructor. Even if I tried compiling Qt that way it would not change anything, since there is no implementation for these two methods, so symbols wouldn't be exported anyways. But the main problem is that I don't know why the kde3support classes seek these symbols, I couldn't find any reference in the code for these symbols? I certantly want to help, since I believe you guys do the good job, making such an excellent desktop. I'we been using KDE for many years now. I also believe enabling the kde4libs on win32 can gain momentum to opensource and linux development. Thx for the informations. I'll try to recompile kde3support in the next few days and take a look what's going wrong there. Christian btw: You'll need some patches for your Qt to compile kdelibs4 - see http://websvn.kde.org/trunk/qt-copy/patches/ - at least 0112 is needed afaik. -- Bis zu 70% Ihrer Onlinekosten sparen: GMX SmartSurfer! Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Fwd: KDE/kdebase/libkonq
Von: Thiago Macieira [EMAIL PROTECTED] Benjamin Reed wrote: On 3/2/06, Thiago Macieira [EMAIL PROTECTED] wrote: On ELF systems using dynamic libraries, where such nonsense is not necessary, don't install the dependency libraries. To our Windows developers: how does MSVC solve such nonsense? Can it link to a DLL without requiring that DLL's dependencies to be listed? Or does it require you to know what dependencies a DLL has? On OSX you have to list all depends, as long as you're using symbols from the dependent library (even indirectly). Which is braindead. Sorry, but it is. If I upgrade a library I use in my simple program and it adds a new dependency, I have to review my program's ld flags. For such brain-damaged systems, the installation of an .la file is a requirement. I don't think this is needed on win32 - otherwise we would had to link kdelibs against win32 system libs what we're not doing. Christian -- Bis zu 70% Ihrer Onlinekosten sparen: GMX SmartSurfer! Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
[mingw] kdoctools linkage problem
Hi, Info: resolving _xmlLoadExtDtdDefaultValue by linking to __imp__xmlLoadExtDtdDefaultValue (auto-import) Info: resolving _xmlIndentTreeOutput by linking to __imp__xmlIndentTreeOutput (auto-import) fu70.o(.idata$3+0xc): undefined reference to `libxml2_dll_a_iname' fu72.o(.idata$3+0xc): undefined reference to `libxml2_dll_a_iname' nmth69.o(.idata$4+0x0): undefined reference to `_nm__xmlLoadExtDtdDefaultValue' nmth71.o(.idata$4+0x0): undefined reference to `_nm__xmlIndentTreeOutput' collect2: ld returned 1 exit status make[3]: *** [bin/kio_ghelp.dll] Error 1 I have libxml2 installed. Any ideas? Paulo ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
[mingw] errors
Hi, Some errors: 1. d:/kde/trunk/kdelibs/kioslave/ftp/ftp.cc: In member function `bool Ftp::ftpReadDir(FtpEntry)': d:/kde/trunk/kdelibs/kioslave/ftp/ftp.cc:1605: error: `S_IFSOCK' undeclared (first use this function) d:/kde/trunk/kdelibs/kioslave/ftp/ftp.cc:1605: error: (Each undeclared identifier is reported only once for each function it appears in.) make[2]: *** [kioslave/ftp/CMakeFiles/kio_ftp.dir/ftp.obj] Error 1 Looked at sys/stat.h and S_IFSOCK is indeed not declared (S_IFDIR, etc, are). 2. Info: resolving vtable for KStyleby linking to __imp___ZTV6KStyle (auto-import) CMakeFiles/keramik.dir/keramik.obj(.text$_ZN12KeramikStyleD1Ev[KeramikSt yle::~KeramikStyle()]+0x49): In function `qt_plugin_instance': d:/kde/trunk/kdelibs/kstyles/keramik/keramik.cpp:657: variable 'vtable for KStyle' can't be auto-imported. Please read the documentation for ld's --enable-auto-import for details. CMakeFiles/keramik.dir/keramik.obj(.text$_ZN12KeramikStyleD0Ev[KeramikSt yle::~KeramikStyle()]+0x4e):d:/kde/trunk/kdelibs/kstyles/keramik/keramik .cpp:657: variable 'vtable for KStyle' can't be auto-imported. Please read the documentation for ld's --enable-auto-import for details. CMakeFiles/keramik.dir/keramik.obj(.text$_ZN13KStyleFactoryI12KeramikSty leE6createERK7QString[KStyleFactoryKeramikStyle::create(QString const)]+0x5c0):d:/kde/trunk/kdelibs/kstyles/keramik/keramik.cpp:657: variable 'vtable for KStyle' can't be auto-imported. Please read the documentation for ld's --enable-auto-import for details. collect2: ld returned 1 exit status No comments :) 3. d:/kde/trunk/kdelibs/kinit/kinit.cpp: In function `pid_t launch(int, const char*, const char*, const char*, int, const char*, bool, const char*, bool, const char*)': d:/kde/trunk/kdelibs/kinit/kinit.cpp:404: error: `socketpair' undeclared (first use this function) d:/kde/trunk/kdelibs/kinit/kinit.cpp:404: error: (Each undeclared identifier is reported only once for each function it appears in.) d:/kde/trunk/kdelibs/kinit/kinit.cpp: In function `void init_signals()': d:/kde/trunk/kdelibs/kinit/kinit.cpp:757: error: aggregate `sigaction act' has incomplete type and cannot be defined d:/kde/trunk/kdelibs/kinit/kinit.cpp:785: error: `sigemptyset' undeclared (first use this function) d:/kde/trunk/kdelibs/kinit/kinit.cpp:786: error: `sigaddset' undeclared (first use this function) d:/kde/trunk/kdelibs/kinit/kinit.cpp:787: error: `SIG_UNBLOCK' undeclared (first use this function) d:/kde/trunk/kdelibs/kinit/kinit.cpp:787: error: `sigprocmask' undeclared (first use this function) d:/kde/trunk/kdelibs/kinit/kinit.cpp:788: error: `SA_NOCLDSTOP' undeclared (first use this function) d:/kde/trunk/kdelibs/kinit/kinit.cpp:796: error: invalid use of undefined type `struct sigaction' d:/kde/trunk/kdelibs/kinit/kinit.cpp:757: error: forward declaration of `struct sigaction' d:/kde/trunk/kdelibs/kinit/kinit.cpp:803: error: invalid use of undefined type `struct sigaction' d:/kde/trunk/kdelibs/kinit/kinit.cpp:757: error: forward declaration of `struct sigaction' make[2]: *** [kinit/CMakeFiles/kdeinit.dir/kinit.obj] Error 1 make[2]: Leaving directory `/d/kde/trunk/kdelibs' AFAIK, windows doesn't support socketpair... Paulo ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: [mingw] errors
Paulo Jorge Guedes wrote: Hi, Some errors: 1. d:/kde/trunk/kdelibs/kioslave/ftp/ftp.cc: In member function `bool Ftp::ftpReadDir(FtpEntry)': d:/kde/trunk/kdelibs/kioslave/ftp/ftp.cc:1605: error: `S_IFSOCK' undeclared (first use this function) d:/kde/trunk/kdelibs/kioslave/ftp/ftp.cc:1605: error: (Each undeclared identifier is reported only once for each function it appears in.) make[2]: *** [kioslave/ftp/CMakeFiles/kio_ftp.dir/ftp.obj] Error 1 Looked at sys/stat.h and S_IFSOCK is indeed not declared (S_IFDIR, etc, are). Is you kdewin32 installation up to date? S_IFSOCK is defined in win/include/wingw/sys/stat.h: http://websvn.kde.org/trunk/KDE/kdelibs/win/include/mingw/sys/stat.h?rev=511668view=markup 2. Info: resolving vtable for KStyleby linking to __imp___ZTV6KStyle (auto-import) CMakeFiles/keramik.dir/keramik.obj(.text$_ZN12KeramikStyleD1Ev[KeramikSt yle::~KeramikStyle()]+0x49): In function `qt_plugin_instance': d:/kde/trunk/kdelibs/kstyles/keramik/keramik.cpp:657: variable 'vtable for KStyle' can't be auto-imported. Please read the documentation for ld's --enable-auto-import for details. CMakeFiles/keramik.dir/keramik.obj(.text$_ZN12KeramikStyleD0Ev[KeramikSt yle::~KeramikStyle()]+0x4e):d:/kde/trunk/kdelibs/kstyles/keramik/keramik .cpp:657: variable 'vtable for KStyle' can't be auto-imported. Please read the documentation for ld's --enable-auto-import for details. CMakeFiles/keramik.dir/keramik.obj(.text$_ZN13KStyleFactoryI12KeramikSty leE6createERK7QString[KStyleFactoryKeramikStyle::create(QString const)]+0x5c0):d:/kde/trunk/kdelibs/kstyles/keramik/keramik.cpp:657: variable 'vtable for KStyle' can't be auto-imported. Please read the documentation for ld's --enable-auto-import for details. collect2: ld returned 1 exit status No comments :) 3. d:/kde/trunk/kdelibs/kinit/kinit.cpp: In function `pid_t launch(int, const char*, const char*, const char*, int, const char*, bool, const char*, bool, const char*)': d:/kde/trunk/kdelibs/kinit/kinit.cpp:404: error: `socketpair' undeclared (first use this function) d:/kde/trunk/kdelibs/kinit/kinit.cpp:404: error: (Each undeclared identifier is reported only once for each function it appears in.) d:/kde/trunk/kdelibs/kinit/kinit.cpp: In function `void init_signals()': d:/kde/trunk/kdelibs/kinit/kinit.cpp:757: error: aggregate `sigaction act' has incomplete type and cannot be defined d:/kde/trunk/kdelibs/kinit/kinit.cpp:785: error: `sigemptyset' undeclared (first use this function) d:/kde/trunk/kdelibs/kinit/kinit.cpp:786: error: `sigaddset' undeclared (first use this function) d:/kde/trunk/kdelibs/kinit/kinit.cpp:787: error: `SIG_UNBLOCK' undeclared (first use this function) d:/kde/trunk/kdelibs/kinit/kinit.cpp:787: error: `sigprocmask' undeclared (first use this function) d:/kde/trunk/kdelibs/kinit/kinit.cpp:788: error: `SA_NOCLDSTOP' undeclared (first use this function) d:/kde/trunk/kdelibs/kinit/kinit.cpp:796: error: invalid use of undefined type `struct sigaction' d:/kde/trunk/kdelibs/kinit/kinit.cpp:757: error: forward declaration of `struct sigaction' d:/kde/trunk/kdelibs/kinit/kinit.cpp:803: error: invalid use of undefined type `struct sigaction' d:/kde/trunk/kdelibs/kinit/kinit.cpp:757: error: forward declaration of `struct sigaction' make[2]: *** [kinit/CMakeFiles/kdeinit.dir/kinit.obj] Error 1 make[2]: Leaving directory `/d/kde/trunk/kdelibs' AFAIK, windows doesn't support socketpair... Paulo kinit also does not compile with msvc. Peter ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Fwd: KDE/kdebase/libkonq
On Thursday 02 March 2006 15:11, Thiago Macieira wrote: Benjamin Reed wrote: On 3/2/06, Thiago Macieira [EMAIL PROTECTED] wrote: On ELF systems using dynamic libraries, where such nonsense is not necessary, don't install the dependency libraries. To our Windows developers: how does MSVC solve such nonsense? Can it link to a DLL without requiring that DLL's dependencies to be listed? Or does it require you to know what dependencies a DLL has? On OSX you have to list all depends, as long as you're using symbols from the dependent library (even indirectly). Which is braindead. Sorry, but it is. If I upgrade a library I use in my simple program and it adds a new dependency, I have to review my program's ld flags. For such brain-damaged systems, the installation of an .la file is a requirement. So does this mean if I link to kparts and use QString in my app, I have to add QtCore explicitely. But as long as I don't call any functions from zlib directly, I don't have to add it, right ? Seems bearable to me. This would mean la files are not required. Bye Alex -- Work: alexander.neundorf AT jenoptik.com - http://www.jenoptik-los.de Home: neundorf AT kde.org- http://www.kde.org alex AT neundorf.net - http://www.neundorf.net ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
Re: Fwd: KDE/kdebase/libkonq
Alexander Neundorf wrote: But I don't think we should do that. Yes, but adding these libs would be no problem in kdelibs/cmake/modules/FindKDE4Internal.cmake . That's not what I meant. Yes, please add them to the kdelibs files. What I meant was that the author of an application outside kdelibs should remember to add QtCore, kdecore, kdeui, etc. to his own dependency list. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 2. Tó cennan his weorc gearu, ymbe se circolwyrde, wearð se cægbord and se leohtspeccabord, and þa mýs cómon lator. On þone dæg, he hine reste. pgpKxwJeITNHz.pgp Description: PGP signature ___ Kde-buildsystem mailing list Kde-buildsystem@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem
