[vsipl++] I'm having trouble using Sourcery VSIPL++
Jules Bergmann
jules at codesourcery.com
Tue Mar 27 21:06:15 UTC 2007
Son,
I just wanted to check in on how VSIPL++ is working for you. Was our
feedback helpful in solving your problem? Definitely let me know if you
are having any issues using VSIPL++.
Also, we're considering how to improve VSIPL++ support for Windows and
wanted to get feedback from Windows users. If you don't mind answering
a few questions, that would be great!
* What types of applications are you developing? Are they intended to
run on Windows in production, or do you use Windows to develop
applications for embedded hardware?
* What signal and image processing libraries do you currently use?
* What Windows development tools do you use? Compilers, IDEs,
debuggers, etc.
* Is the use of Intel C++ on Windows acceptable for your development,
assuming that it is integrated in to the Visual IDE?
* Would you consider using GCC based tools if they were integrated into
the Eclipse IDE?
Please feel free to give me a call at 650-704-4014.
thanks,
-- Jules
Stefan Seefeld wrote:
> sonho4 at comcast.net wrote:
>>
>> 1) I downloaded the VSIPL++ Binary package (IA32 Microsoft Windows XP),
>> sourceryvsipl++-1.2-win-x86 (WinZip file), from
>> http://www.codesourcery.com/vsiplplusplus/1.2/download.html to my WinXP
>> laptop computer.
>>
>> 2) Also, I installed the Intel(R) C++ Compiler for 32-bit applications,
>> Version 9.1 (evaluation copy) on my laptop computer.
>>
>> 3) I unzipped the VSIPL++ binary package.
>>
>> 4) I tried to compile and run /share/sourceryvsipl++/example1.cpp
>> *without success.*
>
> The Makefile in that directory assumes a UNIX-like environment with
> tools such as pkg-config to extract build parameters from pre-built
> and packaged configuration files. Unfortunately, that strategy isn't
> supported on Windows, where these tools don't exist.
>
> Instead, it is assumed that you use some platform-specific build
> environment (such as the MSVC IDE), where you manually add build
> parameters, such as installation paths for third-party libraries
> that are used in conjunction with Sourcery VSIPL++.
>
> We are working on ways to enhance this for future releases.
>
>> Please look at the following compilation output and tell me what's wrong.
>>
>> The last error showed the header file, mkl_cblas.h, was not found.
>> The *VSIPL++ binary package does not contain mkl_cblas.h*. Should I go
>> somewhere else to get this missing header file?
>
> The Windows version of Sourcery VSIPL++ is built using Intel's
> IPP and MKL libraries (see
> http://www.codesourcery.com/public/vsiplplusplus/sourceryvsipl++-1.2/quickstart/chap-installation.html#id287819
> for more information on these).
> We are looking into how to remove that restriction, i.e. to make IPP and MKL
> optional, like they are on other platforms.
>
> Regards,
> Stefan
>
--
Jules Bergmann
CodeSourcery
jules at codesourcery.com
(650) 331-3385 x705
More information about the vsipl++
mailing list