-
Yeah, dumb error - i was still including the unedited fwbase.h header, thanks for your help,
and for making Framewave available, its proving very useful!
If i had one request it would be for a 1d FFT, as im using it to mirror the vDSP framework on OSX,
and that has a pretty decent FFT implementation.
2009-07-09 13:17:40 UTC in Framewave
-
Tried a clean build of Framewave using the MD/Gd settings, used a different project, got 8 missing symbols errors, strange, the project builds ok when Framewave is built MD/Gz.
1>CTemplate.obj : error LNK2019: unresolved external symbol _fwsConvert_64f32f@12 referenced in function "void __cdecl vDSP_vdpsp(double const * const,int,float * const,int,int)"...
2009-07-09 03:11:19 UTC in Framewave
-
Those are the errors i get after trying to link to the libs in VC++ 2005. The project is compiled as /MD /Gd, i'm using other Framewave functions in the source, so some symbols are found but these three are not, of note is that they all have 64bit/doubles in common.
2009-07-07 01:05:55 UTC in Framewave
-
hmm, spoke too soon, when i try to link to the MD/Gd libs i get unresolved symbol errors:
error LNK2019: unresolved external symbol _fwsConvert_64f32f
error LNK2019: unresolved external symbol _fwsConvert_32f64
error LNK2019: unresolved external symbol _fwsMulC_64f.
2009-07-03 13:15:15 UTC in Framewave
-
Thanks, that worked,
but i had to edit Framewave\domain\fwBase\include\fwBase.h not
Framewave\build\include\fwBase.h otherwisei got a compile error.
2009-07-03 12:45:55 UTC in Framewave
-
Is it possible to build Framewave as /MD /Gd rather than the default /MT /Gz
i need the calling convention and link style to match with a VC++ project.
I tried setting these flags in fwflags_msvc.py, fwBase.libf was ok but wSignal.lib wouldnt build.
2009-06-26 13:29:25 UTC in Framewave
