[vsipl++] fftm compile problem

[Day, John]

Stefan wrote:
>> You mention the windows binary release, which is configured / compiled
>> for use with Intel's IPP and MKL libraries. But then you are talking about
>> the source distribution, and mingw. To help you a little further it
>> is important to know what Sourcery VSIPL++ package you use .....
 
At first I tried to build the source distribution using MinGW and g++ 3.4.5, but the build failed trying to configure ATLAS and I was not able to produce the config files.
 
So then I tried using the IA32 binary, just to see if I could compile the example fft.cpp (and the BeamformEx files) from the MS-DOS command line:
 
> g++ -c -I/usr/local/include fft.cpp
 
That's when the error occurred. I did not configure the fft backends or anything else. Nor did I expect the link step to work because there are no .a libraries in the Windows binary. 
 
I suppose I will have to set up a Cygwin environment, but I was hoping that MinGW alone would work.
 
Tnx,
John Day

________________________________

From: Stefan Seefeld [mailto:stefan at codesourcery.com]
Sent: Tue 6/26/2007 7:27 PM
To: Day, John
Cc: vsipl++ at codesourcery.com
Subject: Re: [vsipl++] fftm compile problem



Hello John,

Day, John wrote:
> Hello,
>
> I am trying out vsipl++ 1.3 !A32 binary for Windows/XP and am having a
> problem instantiating the fftm templates in your fft.cpp code example
> (from the source distribution).
>
> I using MinGW with g++ 3.4.5 and I am getting "error: no type named
> `first' in `struct vsip::impl::fft::LibraryTagList'"  (see below for all
> messages). I suspect this has something to do with
> vsip/opt/dispatch.hpp, but I don't know enough about the architecture to
> figure out how to fix it.

You are right, the problem is related to the dispatch mechanism we use to
delegate calls to backends. In this case, it sounds as if you haven't
configured any fft backends.
You mention the windows binary release, which is configured / compiled
for use with Intel's IPP and MKL libraries. But then you are talking about
the source distribution, and mingw. To help you a little further it
is important to know what Sourcery VSIPL++ package you use, and how exactly
the command looks that raises the error. Are you configuring / building
Sourcery VSIPL++ yourself ? What commands are you using ?

Thanks,
                Stefan


--
Stefan Seefeld
CodeSourcery
stefan at codesourcery.com
(650) 331-3385 x718
 
 
 
 
 
 
 
This electronic message and any files transmitted with it contain information which may be privileged and/or proprietary. The information is intended for use solely by the intended recipient(s). If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of this information is prohibited. If you have received this electronic message in error, please advise the sender by reply email or by telephone (301-939-7000) and delete the message.