headers
Gilles Caulier | 1 Sep 2010 17:02
Picon
Gravatar

linking failure with digiKam and nmake

Hi all.

I processing code fix to compile fine digiKam & co under M$ Windows 7.
I compile it with :

- KDE 4.4.4 devel packages
- M$ Visual C++ 2008 Pro

I compile and link sucessfully  exiv2, libkdcraw, libkipi, libkexiv2 from trunk

When i process digiKam from trunk, i can see this error message :

directorynameoption.cpp
[ 45%] Building CXX object
digikam/digikam/CMakeFiles/digikam.dir/__/utilities/advancedrename/parser/options/filepropertiesoption.ob
j
filepropertiesoption.cpp
[ 45%] Building CXX object
digikam/digikam/CMakeFiles/digikam.dir/__/utilities/advancedrename/parser/options/metadataoption.obj
metadataoption.cpp
[ 45%] Building CXX object
digikam/digikam/CMakeFiles/digikam.dir/__/utilities/advancedrename/parser/options/sequencenumberoption.ob
j
sequencenumberoption.cpp
[ 45%] Building CXX object
digikam/digikam/CMakeFiles/digikam.dir/__/libs/widgets/common/databasewidget.obj
databasewidget.cpp
[ 45%] Building CXX object
digikam/digikam/CMakeFiles/digikam.dir/__/libs/dialogs/migrationdlg.obj
migrationdlg.cpp
(Continue reading)

Permalink | Reply | 28 comments |
headers
Andrew Goodbody | 2 Sep 2010 00:08
Picon
Favicon

Re: linking failure with digiKam and nmake

On 01/09/2010 16:02, Gilles Caulier wrote:
> Linking CXX executable ..\..\bin\digikam.exe
> fatal error C1900: incompatibilitÚ de IL entre 'P1' version '20080116'
> et 'P2' version '20070207'

http://social.msdn.microsoft.com/Forums/en-US/vclanguage/thread/9abfefe0-56bd-4a82-ae14-b08f262972bd

Install SP1 for VS2008
http://www.microsoft.com/downloads/details.aspx?familyid=FBEE1648-7106-44A7-9649-6D9F6D58056E&displaylang=en

HTH,
Andrew
Permalink | Reply | 27 comments |
headers
Gilles Caulier | 2 Sep 2010 09:40
Picon
Gravatar

Re: linking failure with digiKam and nmake

Thanks a lots Andrew. I test it now on my computer...

Gilles Caulier

2010/9/2 Andrew Goodbody <ajg02@...>:
> On 01/09/2010 16:02, Gilles Caulier wrote:
>> Linking CXX executable ..\..\bin\digikam.exe
>> fatal error C1900: incompatibilitÚ de IL entre 'P1' version '20080116'
>> et 'P2' version '20070207'
>
> http://social.msdn.microsoft.com/Forums/en-US/vclanguage/thread/9abfefe0-56bd-4a82-ae14-b08f262972bd
>
> Install SP1 for VS2008
> http://www.microsoft.com/downloads/details.aspx?familyid=FBEE1648-7106-44A7-9649-6D9F6D58056E&displaylang=en
>
> HTH,
> Andrew
> _______________________________________________
> Kde-windows mailing list
> Kde-windows@...
> https://mail.kde.org/mailman/listinfo/kde-windows
>
Permalink | Reply | 3 comments |
headers
Gilles Caulier | 2 Sep 2010 09:44
Picon
Gravatar

Re: linking failure with digiKam and nmake

M$ Visual C++ 2010 fix this problem ? Can i use it as well to compile
and debug digiKam under windows ?

Do you tried this version with KDE-Windows project ?

Gilles Caulier

2010/9/2 Gilles Caulier <caulier.gilles@...>:
> Thanks a lots Andrew. I test it now on my computer...
>
> Gilles Caulier
>
> 2010/9/2 Andrew Goodbody <ajg02@...>:
>> On 01/09/2010 16:02, Gilles Caulier wrote:
>>> Linking CXX executable ..\..\bin\digikam.exe
>>> fatal error C1900: incompatibilitÚ de IL entre 'P1' version '20080116'
>>> et 'P2' version '20070207'
>>
>> http://social.msdn.microsoft.com/Forums/en-US/vclanguage/thread/9abfefe0-56bd-4a82-ae14-b08f262972bd
>>
>> Install SP1 for VS2008
>> http://www.microsoft.com/downloads/details.aspx?familyid=FBEE1648-7106-44A7-9649-6D9F6D58056E&displaylang=en
>>
>> HTH,
>> Andrew
>> _______________________________________________
>> Kde-windows mailing list
>> Kde-windows@...
>> https://mail.kde.org/mailman/listinfo/kde-windows
>>
(Continue reading)

Permalink | Reply | 2 comments |
headers
Andreas Holzammer | 2 Sep 2010 09:52
Favicon

Re: linking failure with digiKam and nmake

Hi Gilles,

Am 02.09.2010 09:44, schrieb Gilles Caulier:
> M$ Visual C++ 2010 fix this problem ? Can i use it as well to compile
> and debug digiKam under windows ?
> 
> Do you tried this version with KDE-Windows project ?
yes i have tried it, there is one issue left in dbus that prevents
compiling kde-windows. There could be also some minor issues, but they
are fixable. If i remember correctly there was a problem with boost.
> 
> Gilles Caulier
> 
> 2010/9/2 Gilles Caulier <caulier.gilles@...>:
>> Thanks a lots Andrew. I test it now on my computer...
>>
>> Gilles Caulier
>>
>> 2010/9/2 Andrew Goodbody <ajg02@...>:
>>> On 01/09/2010 16:02, Gilles Caulier wrote:
>>>> Linking CXX executable ..\..\bin\digikam.exe
>>>> fatal error C1900: incompatibilitÚ de IL entre 'P1' version '20080116'
>>>> et 'P2' version '20070207'
>>>
>>> http://social.msdn.microsoft.com/Forums/en-US/vclanguage/thread/9abfefe0-56bd-4a82-ae14-b08f262972bd
>>>
>>> Install SP1 for VS2008
>>> http://www.microsoft.com/downloads/details.aspx?familyid=FBEE1648-7106-44A7-9649-6D9F6D58056E&displaylang=en
>>>
>>> HTH,
(Continue reading)

Permalink | Reply | 1 comment |
headers
Gilles Caulier | 2 Sep 2010 10:06
Picon
Gravatar

Re: linking failure with digiKam and nmake

Great to hear.

I would to improve digiKam and co support under windows. I recieve a
lots of mail and blogs post about to have a suitable digiKam release
with M$ OS.

My contribution to kde-windows is limited, but i can check compilation
with MSVC and MinGW.

I also recieve some bug report about digiKam under windows. All are
about 1.1.0 release which is really old now (1.4.0 just released).
This is why i would to see last stable code packaged in kde-windows
project.

I also written a tutorial to describe how i compile digiKam under
windows. Take a look here, and especially all users messages :

http://www.digikam.org/drupal/node/525

Let's me hear how i can help you in this way.

Gilles Caulier

2010/9/2 Andreas Holzammer <Andreas.Holzammer@...>:
> Hi Gilles,
>
> Am 02.09.2010 09:44, schrieb Gilles Caulier:
>> M$ Visual C++ 2010 fix this problem ? Can i use it as well to compile
>> and debug digiKam under windows ?
>>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gilles Caulier | 2 Sep 2010 11:34
Picon
Gravatar

Re: linking failure with digiKam and nmake

Ok, now linking pass, but with a warning... Look there :

[ 45%] Building RC object digikam/digikam/CMakeFiles/digikam.dir/digikam.res
Microsoft (R) Windows (R) Resource Compiler Version 6.1.6723.1
Copyright (C) Microsoft Corporation.  All rights reserved.

Linking CXX executable ..\..\bin\digikam.exe
qtmain.lib(qtmain_win.obj) : .netmodule ou module MSIL compilÚ avec
/GL trouvÚá; redÚmarrage de l'Údition de liens avec /LTCGá; ajou
tez /LTCG Ó la ligne de commande de l'Údition de liens pour amÚliorer
les performances de l'╔diteur de liens
LINK : warning LNK4075: ' /INCREMENTAL' ignorÚ Ó cause de la
spÚcification '/LTCG'
   CrÚation de la bibliothÞque ..\..\bin\digikam.lib et de l'objet
..\..\bin\digikam.exp
msvcrtd.lib(cinitexe.obj) : warning LNK4098: conflit entre la
bibliothÞque par dÚfaut 'msvcrt.lib' et les autres bibliothÞquesá; uti
lisez /NODEFAULTLIB:library
GÚnÚration de code en cours
Fin de la gÚnÚration du code
qtmain.lib(qtmain_win.obj) : .netmodule ou module MSIL compilÚ avec
/GL trouvÚá; redÚmarrage de l'Údition de liens avec /LTCGá; ajou
tez /LTCG Ó la ligne de commande de l'Údition de liens pour amÚliorer
les performances de l'╔diteur de liens
LINK : warning LNK4075: ' /INCREMENTAL' ignorÚ Ó cause de la
spÚcification '/LTCG'
   CrÚation de la bibliothÞque ..\..\bin\digikam.lib et de l'objet
..\..\bin\digikam.exp
msvcrtd.lib(cinitexe.obj) : warning LNK4098: conflit entre la
bibliothÞque par dÚfaut 'msvcrt.lib' et les autres bibliothÞquesá; uti
(Continue reading)

Permalink | Reply | 22 comments |
headers
Gilles Caulier | 2 Sep 2010 12:46
Picon
Gravatar

Re: linking failure with digiKam and nmake

Note : whole digiKam and kipi-plugins compile fine now with MSVC 2008

Gilles Caulier

Le 2 septembre 2010 11:34, Gilles Caulier <caulier.gilles <at> gmail.com> a écrit :
> Ok, now linking pass, but with a warning... Look there :
>
> [ 45%] Building RC object digikam/digikam/CMakeFiles/digikam.dir/digikam.res
> Microsoft (R) Windows (R) Resource Compiler Version 6.1.6723.1
> Copyright (C) Microsoft Corporation.  All rights reserved.
>
> Linking CXX executable ..\..\bin\digikam.exe
> qtmain.lib(qtmain_win.obj) : .netmodule ou module MSIL compilÚ avec
> /GL trouvÚá; redÚmarrage de l'Údition de liens avec /LTCGá; ajou
> tez /LTCG Ó la ligne de commande de l'Údition de liens pour amÚliorer
> les performances de l'╔diteur de liens
> LINK : warning LNK4075: ' /INCREMENTAL' ignorÚ Ó cause de la
> spÚcification '/LTCG'
>   CrÚation de la bibliothÞque ..\..\bin\digikam.lib et de l'objet
> ..\..\bin\digikam.exp
> msvcrtd.lib(cinitexe.obj) : warning LNK4098: conflit entre la
> bibliothÞque par dÚfaut 'msvcrt.lib' et les autres bibliothÞquesá; uti
> lisez /NODEFAULTLIB:library
> GÚnÚration de code en cours
> Fin de la gÚnÚration du code
> qtmain.lib(qtmain_win.obj) : .netmodule ou module MSIL compilÚ avec
> /GL trouvÚá; redÚmarrage de l'Údition de liens avec /LTCGá; ajou
> tez /LTCG Ó la ligne de commande de l'Údition de liens pour amÚliorer
> les performances de l'╔diteur de liens
> LINK : warning LNK4075: ' /INCREMENTAL' ignorÚ Ó cause de la
(Continue reading)

Permalink | Reply | 3 comments |
headers
Gilles Caulier | 2 Sep 2010 13:22
Picon
Gravatar

Re: linking failure with digiKam and nmake

digiKam crash after to set-up first run assistant. Crash appear in
libkipi after than kipi-plugins instance is created. Look the
backtrace :

 	msvcr90d.dll!_free_dbg_nolock(void * pUserData=0x0a215da0, int
nBlockUse=1730199736)  Ligne 1323 + 0x54 octets	C++
 	msvcr90d.dll!_free_dbg(void * pUserData=0x0a215da0, int
nBlockUse=1730199736)  Ligne 1258 + 0xd octets	C++
 	msvcr90d.dll!operator delete(void * pUserData=0x0a215da0)  Ligne 54
+ 0x10 octets	C++
 	kipi.dll!KSharedPtr<KService>::`scalar deleting destructor'()  +
0x27 octets	C++
 	kipi.dll!QList<KSharedPtr<KService>
>::node_destruct(QList<KSharedPtr<KService> >::Node * from=0x1ccec46c,
QList<KSharedPtr<KService> >::Node * to=0x1ccec4cc)  Ligne 402 + 0x2f
octets	C++
 	kipi.dll!QList<KSharedPtr<KService> >::free(QListData::Data *
data=0x1ccec458)  Ligne 648	C++
 	kipi.dll!QList<KSharedPtr<KService> >::~QList<KSharedPtr<KService>
>()  Ligne 622	C++
>	kipi.dll!KIPI::PluginLoader::construct(const QStringList & ignores={...}, KIPI::Interface *
const interface=0x063f05f0, const QString & constraint={...})  Ligne 329 + 0x31 octets	C++
 	kipi.dll!KIPI::PluginLoader::PluginLoader(const QStringList &
ignores={...}, KIPI::Interface * const interface=0x063f05f0)  Ligne
269 + 0x33 octets	C++
 	digikam.exe!Digikam::DigikamApp::loadPlugins()  Ligne 2311 + 0x33 octets	C++
 	digikam.exe!Digikam::DigikamApp::DigikamApp()  Ligne 254	C++
 	digikam.exe!main(int argc=1, char * * argv=0x06127250)  Ligne 172 +
0x2a octets	C++
 	digikam.exe!_WinMain <at> 16()  + 0x9e octets	C++
(Continue reading)

Permalink | Reply | 2 comments |
headers
Gilles Caulier | 2 Sep 2010 13:31
Picon
Gravatar

Re: linking failure with digiKam and nmake

With Showfoto, i can see a similar crash when an imageplugin is loaded
in editor :

>	msvcr90d.dll!operator delete(void * pUserData=0x0cf188c0)  Ligne 52 + 0x51 octets	C++
 	digikamlib.dll!KSharedPtr<KService>::`scalar deleting destructor'()
+ 0x27 octets	C++
 	digikamlib.dll!QList<KSharedPtr<KService>
>::node_destruct(QList<KSharedPtr<KService> >::Node * from=0x0f9a53b4,
QList<KSharedPtr<KService> >::Node * to=0x0f9a53c4)  Ligne 402 + 0x2f
octets	C++
 	digikamlib.dll!QList<KSharedPtr<KService> >::free(QListData::Data *
data=0x0f9a53a0)  Ligne 648	C++
 	digikamlib.dll!QList<KSharedPtr<KService>
>::~QList<KSharedPtr<KService> >()  Ligne 622	C++
 	digikamlib.dll!Digikam::ImagePluginLoader::ImagePluginLoader(QObject
* parent=0x04def460, Digikam::SplashScreen * splash=0x04e00a98)  Ligne
144 + 0xc octets	C++
 	showfoto.exe!ShowFoto::ShowFoto::ShowFoto(const KUrl::List &
urlList={...})  Ligne 228 + 0x3c octets	C++
 	showfoto.exe!main(int argc=1, char * * argv=0x04b89128)  Ligne 80 +
0x31 octets	C++
 	showfoto.exe!_WinMain <at> 16()  + 0x9e octets	C++
 	showfoto.exe!__tmainCRTStartup()  Ligne 578 + 0x35 octets	C
 	showfoto.exe!WinMainCRTStartup()  Ligne 403	C
 	kernel32.dll!75e43677() 	
 	[Les frames ci-dessous sont peut-être incorrects et/ou manquants,
aucun symbole chargé pour kernel32.dll]
 	ntdll.dll!77649d72() 	
 	ntdll.dll!77649d45()
(Continue reading)

Permalink | Reply | 0 comments |

Gmane