[Stk] Tentative question - porting Stk

[Perry R Cook]

My original intention was to help enable exactly that.
I made the inner loops (tick functions) as ANSI-C-like
as possible.  I had #define MY_FLOAT and other things
that might be different word sizes on DSPs vs. bigger
processors.   I didn't vectorize because I didn't want
to, but some have done it for efficiency.  Gary has
recently put in more hooks to support vectorization.

It should be pretty easy to get an instrument or two
running, once you work out the compiler issues.

PRC

On Sat, 5 Nov 2005, Ross Clement wrote:

> Hi. Could anyone comment on how difficult it might be to port Stk to
> other platforms? In particular, I'm looking around at DSP chips that can
> be used to build small physical devices.
>
> Note that the following "IFs" are VERY BIG IFs.
>
> IF I found such a processor and IF that processor had a C++ compiler
> available and IF [to be honest] I could interest a student in doing so
> for their project THEN porting Stk to a processor/board combo designed
> here would be an interesting thing to do. I note that most Stk classes
> are platform independent, but am wondering how much would have to be
> changed.
>
> Any comments on the difficulty of porting Stk? Due to all the IFs I'm
> only looking for single sentence overviews, not detailed plans.
>
> Cheers,
>
> Ross-c
>
> _______________________________________________
> Stk mailing list
> Stk@ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/stk
>