On Thu, Sep 18, 2014 at 7:28 AM, Dominique Fober <fo...@grame.fr> wrote:
> one reason is the light weight of the library, but you’re right regarding
> the dozens of faust dsps.
> another one is the standalone binary, which makes remote distribution more
> straightforward (especially in case of web services)
>
I understand that there are use cases for static linking of plugins, too --
that's fine, they can both be included in the packages.
I’ll modify the scripts in order to optionally compile as a shared library.
>
Cool, many thanks! :)
BTW, Stephane, I think that it would a good idea to pull the changes
necessary to make 'make dynamic' work on Linux from faust2 to mainline
faust. The 'make sound2faust' target in mainline faust also needs fixing
(missing -I../../architecture) so that it compiles without having to
install faust first. Should I just go ahead with this or do you want to
take care of it?
And there's still a bigger issue with faust2 on LLVM 3.5, which has been
out for a few weeks and is already available in Arch and on OS X (via
MacPorts). This affects my faust2 packages for Arch, in particular. While
we already have some preliminary support for LLVM 3.5 in the Makefiles,
Faust2 doesn't compile with LLVM 3.5 proper yet due to numerous changes in
LLVM's C++ API. I already started working on these, should I commit the
changes that I have as I go along?
Albert
--
Dr. Albert Gr"af
Computer Music Research Group, JGU Mainz, Germany
Email: aggr...@gmail.com
WWW: https://plus.google.com/+AlbertGraef
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Faudiostream-devel mailing list
Faudiostream-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/faudiostream-devel
