- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My company bought the IPP 4.1 for windows and try to integrate it in our product. Now I have two questions in customize IPP DLLs
============================================================
1. When I follow the intel's example,......
I follow the readme.htm in
c:Program FilesIntelIPP41ia32_itanium oolscustomdll eadme.htm
and I only changed the tools.ini as following:
CL_ENV=OFF #Original is ON
MSVCDir=C:Program FilesMicrosoft Visual Studio .NET 2003Vc7
DllName=jiing
TestName=ipptwo_jiing
and when I change to the directory and execute nmake
C:Program FilesIntelIPP41ia32_itanium oolscustomdll>nmake
The error happened
tools.ini(57) : fatal error U1033: syntax error : '""C:Program'
unexpected
Stop.
====================================================================
tools.ini (58) is
! IF !EXIST ("$(MSVCDir)")
So I guess the MSVCDir has some problems, and decide to replace all the
$(MSVCDir) as C:Program FilesMicrosoft Visual Studio .NET 2003Vc7 in
tools.ini, and comment the follow lines in tools.ini
# check if MSVC path is accessible
#!IF "$(CL_ENV)"=="OFF"
#! IF !EXIST ("$(MSVCDir)")
#! ERROR Path to MSVC is not found! Check the MSVCDir in tools.ini
#! ENDIF
#!ENDIF
The result is:
C:Program FilesIntelIPP41ia32_itanium oolscustomdll>nmake
Microsoft Program Maintenance Utility Version 1.50
Copyright (c) Microsoft Corp 1988-94. All rights reserved.
nmake /nologo -f customdll.mak
"C:Program FilesMicrosoft Visual Studio .NET
2003Vc7incl.exe" /nologo /c /GB /W3 /O2 -I"....in
clude" -I"C:Program FilesMicrosoft Visual Studio .NET
2003Vc7include" /D "NDEBUG" /D "WIN32" /D "_WINDOWS"
-MD /DPX /DA6 /DW7 /DT7 /Fo".Libjiing.obj" dllmain.c
'C:Program'
?????????????????????
(jiing: The above in Chinese means C:Program is not internal or
external command, executable or batch files)
NMAKE : fatal error U1077: 'C:WINDOWSsystem32cmd.exe' : return code
'0x1'
Stop.
NMAKE : fatal error U1077: 'C:WINDOWSsystem32cmd.exe' : return code
'0x2'
Stop.
Could anyone give me some suggestions? Thank you.
==================================================================
2. If we successfully customize the IPP DLLs, should we still give our customer the IPP runtime to install, or just use our custom IPP DLLs, or some other method. Could we do not show the IPP runtime installing screen in our installing process?
Thanks in advance.
=======================================================================
-jiing-
============================================================
1. When I follow the intel's example,......
I follow the readme.htm in
c:Program FilesIntelIPP41ia32_itanium oolscustomdll eadme.htm
and I only changed the tools.ini as following:
CL_ENV=OFF #Original is ON
MSVCDir=C:Program FilesMicrosoft Visual Studio .NET 2003Vc7
DllName=jiing
TestName=ipptwo_jiing
and when I change to the directory and execute nmake
C:Program FilesIntelIPP41ia32_itanium oolscustomdll>nmake
The error happened
tools.ini(57) : fatal error U1033: syntax error : '""C:Program'
unexpected
Stop.
====================================================================
tools.ini (58) is
! IF !EXIST ("$(MSVCDir)")
So I guess the MSVCDir has some problems, and decide to replace all the
$(MSVCDir) as C:Program FilesMicrosoft Visual Studio .NET 2003Vc7 in
tools.ini, and comment the follow lines in tools.ini
# check if MSVC path is accessible
#!IF "$(CL_ENV)"=="OFF"
#! IF !EXIST ("$(MSVCDir)")
#! ERROR Path to MSVC is not found! Check the MSVCDir in tools.ini
#! ENDIF
#!ENDIF
The result is:
C:Program FilesIntelIPP41ia32_itanium oolscustomdll>nmake
Microsoft Program Maintenance Utility Version 1.50
Copyright (c) Microsoft Corp 1988-94. All rights reserved.
nmake /nologo -f customdll.mak
"C:Program FilesMicrosoft Visual Studio .NET
2003Vc7incl.exe" /nologo /c /GB /W3 /O2 -I"....in
clude" -I"C:Program FilesMicrosoft Visual Studio .NET
2003Vc7include" /D "NDEBUG" /D "WIN32" /D "_WINDOWS"
-MD /DPX /DA6 /DW7 /DT7 /Fo".Libjiing.obj" dllmain.c
'C:Program'
?????????????????????
(jiing: The above in Chinese means C:Program is not internal or
external command, executable or batch files)
NMAKE : fatal error U1077: 'C:WINDOWSsystem32cmd.exe' : return code
'0x1'
Stop.
NMAKE : fatal error U1077: 'C:WINDOWSsystem32cmd.exe' : return code
'0x2'
Stop.
Could anyone give me some suggestions? Thank you.
==================================================================
2. If we successfully customize the IPP DLLs, should we still give our customer the IPP runtime to install, or just use our custom IPP DLLs, or some other method. Could we do not show the IPP runtime installing screen in our installing process?
Thanks in advance.
=======================================================================
-jiing-
Link Copied
6 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
> The above in Chinese means C:Program is not internal or external command, executable or batch files)
Have you tried changing "Program Files" to "Progra~1" i.e. the DOS short file name syntax. It appears that the error is saying that "Program.exe" or "Program.com" is not a system executable, hence it is not recognising that it is a path. Of course you will have to reformat the full path (i.e. Visual Studio.......).
I have created a custom DLL (only got three functions in it!) and I just distribute the DLL without problems.
Good luck
Chris
Have you tried changing "Program Files" to "Progra~1" i.e. the DOS short file name syntax. It appears that the error is saying that "Program.exe" or "Program.com" is not a system executable, hence it is not recognising that it is a path. Of course you will have to reformat the full path (i.e. Visual Studio.......).
I have created a custom DLL (only got three functions in it!) and I just distribute the DLL without problems.
Good luck
Chris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for your instruction.
But when I change the MSVCDIR to:
MSVCDir=C:Progra~1Microso~VC98
and nmake it again, it show an erro message:
C:Program FilesIntelIPP41ia32_itanium oolscustomdll>nmake
Microsoft Program Maintenance Utility Version 1.50
Copyright (c) Microsoft Corp 1988-94. All rights reserved.
tools.ini(56) : fatal error U1050: Path to MSVC is not found! Check the MSVCDir
in tools.ini
Stop.
But when I change the MSVCDIR to:
MSVCDir=C:Progra~1Microso~VC98
and nmake it again, it show an erro message:
C:Program FilesIntelIPP41ia32_itanium oolscustomdll>nmake
Microsoft Program Maintenance Utility Version 1.50
Copyright (c) Microsoft Corp 1988-94. All rights reserved.
tools.ini(56) : fatal error U1050: Path to MSVC is not found! Check the MSVCDir
in tools.ini
Stop.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I found what's wrong with me.
I guess is that I installed the PXPerl and causing some problems.
when I use a clean computer just with windowsxp+visual studio 6+IPP
then it works but with some error in creating ipptwo test problem
I think it's because I did not revise the test program.
Anyway, it generated the customize dll I needed.
Now, could anyone help me to use the customize dll.
just include the lib and funclist.h seems not work.
thanks in advance.
-jiing-
I guess is that I installed the PXPerl and causing some problems.
when I use a clean computer just with windowsxp+visual studio 6+IPP
then it works but with some error in creating ipptwo test problem
I think it's because I did not revise the test program.
Anyway, it generated the customize dll I needed.
Now, could anyone help me to use the customize dll.
just include the lib and funclist.h seems not work.
thanks in advance.
-jiing-
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
S.Taylor IPP book Chapter 2 has complete detailed explanations for linkage strategy and IPP customisation. Included source code and projects makes this process very simple and does not require complex often obscure policy presented in standard IPP docs. So don't waste time : go to the book.
SRSR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for your response,
I had read the following document and found it's alike as what you mentioned.
http://cache-www.intel.com/cd/00/00/21/93/219301_linkage_models.pdf
Now I have a question:
If I want to use all of the functions in ippcore.h, ipps.h, ippsc.h, ippsr.h. Did I have to customize IPP dll, or just use their respectively Dynamic Linking library, ippcore.lib, ipps20.lib, ippsc20.lib, ippsr20.lib.
Thanks in advance.
-jiing-
I had read the following document and found it's alike as what you mentioned.
http://cache-www.intel.com/cd/00/00/21/93/219301_linkage_models.pdf
Now I have a question:
If I want to use all of the functions in ippcore.h, ipps.h, ippsc.h, ippsr.h. Did I have to customize IPP dll, or just use their respectively Dynamic Linking library, ippcore.lib, ipps20.lib, ippsc20.lib, ippsr20.lib.
Thanks in advance.
-jiing-
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
usually, if can want to create custom DLL to reduce binaries distributed with your application in case you use only few IPP functions. If you extensively use several IPP domains there is no benefits from custom DLL. Note, you also can link your application with static IPP libraries, in this case only those functions which are used in your application will be linked into final binary.
Regards,
Vladimir
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page