IA-32 for Microsoft* Windows* Compiler Compatibility
-
..........
-
Microsoft Visual Studio* 2010
-
Microsoft Visual Studio* 2008
-
Microsoft Visual Studio* 2005
that's mean this versions of IPP were validated with these versions of Microsoft Compiler ...
and correspondingly IPP's libraries were build by one of the latest Intel Compiler (v.12.*) too.
--Gennady
Please try to search the web with "
LNK1000 Visual Studio 98
" expression. Here are two links from the top:
http://support.microsoft.com/kb/948127
http://archive.msdn.microsoft.com/KB948127
Unfortunately, they describe problems with
Visual Studio 2008
.
1.
Could you try to change '
/INCREMENTAL
' to '
/INCREMENTAL:NO
'?
2.
Could you try to install
SP6
for
Visual Studio 98
? ( There is a little hope that it will fix the problem ).
By the way,a
Linker
version installed with
VS98
on my test laptop is
6.00.8447
.
Best regards,
Sergey
Dear Sergey,
Thank you for your help, and I solve the problem finally. Just like I said that there are .debug$S section but not seen .debug$F section after, and I write a small program to modify .debug$S section to .data section, and everything is allright. It build well, and I can turn on Generate debug info option and also /INCREMENTAL. And no need to use higher modern compiler or linker just VC++ 6.0 SP5. Thanks again.
Best Regards,
Andy
I don't use a static linking but I think developers who use the static linking of
IPP
libraries could be
interested to learn more about the problem. You stated that:
...I write a small program to modify
.debug$S
section to
.data
section...
Do you mean that your '
small program
'opened a static library file in a '
binary
' mode and chaged all
'
.debug$S
' expressions to '
.debug$F
'? Is that correct?
Best regards,
Sergey
Dear Sergey,
I'm sorry for answering your question so lately, and opened a static library file in a 'binary' mode is corret, and changed all '.debug$S' expressions to '.data' of IMAGE_SCN_CNT_INITIALIZED_DATA|IMAGE_SCN_ALIGN_16BYTES|IMAGE_SCN_MEM_READ|IMAGE_SCN_MEM_WRITE(0xC0500040) characteristics. I think that correct method is insert a '.debug$F' section after '.text' section, but it'll correct all sections which relate with these section's number.
Best regards,
ANdy
Thank you, Andy!
I understood that your modifications are related toa '
Characteristics
' member of
IMAGE_SECTION_HEADER
structure (declared in
WinNT.h
header ).
...
typedef struct _IMAGE_SECTION_HEADER
{
...
DWORD
Characteristics
;
}
IMAGE_SECTION_HEADER
;
...
and some functions from
ImageHlp
or
DbgHlp
APIhave beenused.
Best regards,
Sergey
Dear Igor:
Yes, you're right butI just need a static library including iPP to link with my old program in Visual C++ 6.0. TheiPP static library does have security cookies, but can write a empty code to link with.Just replace the section talked before and LNK1000 Error is disappear(Generate debug info option is on). Attach a ijl20l.lib below which you can try to link with Visual C++6.0.
Best Regards,
Andy
Andy,
the approach you use is the hackers' one - it will not work correctly for all intended cases of library use - the official way is to use a patch from Microsoft - just install
http://support.microsoft.com/kb/949009
and you'll be able to use old linker version with the latest IPP libraries
Regards,
Igor
Dear Igor,
I take a lookat the link
http://support.microsoft.com/kb/949009
and it just fix VS2005 SP1 not Visual C++ 6.0, and download the files in the page then installedbut it appeared installation error. Beacuse I didn't install VS2005, the installer cannot find VS2005 to patch. I know that my approach is not very correct, but I cannot let Intel to release the iPP static librarycompatible with Visual C++ 6.0. So It's the shortcut to solve the problem, isn't it?
Best Regards,
Andy
Andy,
the approach you use is the hackers' one - it will not work correctly for all intended cases of library use - the official way is to use a patch from Microsoft - just install
http://support.microsoft.com/kb/949009
and you'll be able to use old linker version with the latest IPP libraries
Regards,
Igor
I also couldn't find an update or a fix for
VS98
. Regarding a link provided by Igor. This is what it says:
...
You must have Visual Studio 2005 SP1 installed to apply this hotfix.
...
If Andy's fix works for him this is a great thing even if itlooks like a hack ( and really is! ).
Best regards,
Sergey
周一至周五提供社区支持。请单击
此处
查看其他联系方式。
英特尔不会验证所有解决方案，包括但不限于该社区中可能出现的任何文件传输。对此，英特尔不做任何明确或隐含的担保，包括但不限于对适销性、适用于特定用途和非侵权的隐含担保，以及由履约习惯、交易习惯和贸易惯例引起的任何担保。
关于编译器优化的更多完整信息，请参阅我们的
优化通知
.
