On 06/09/2017 07:06 AM, Stéphane Letz wrote: > > We (at Grame) use static linking for different side projects we maintain, > that is mainly faustgen~ (the Max/MSP external) and FaustLive. For various > deployment reasons, we really prefer having « self-contained » components.
sigh, yes. <rant> there are certainly reasons to prefer static linking: mostly it boils down to convenience (and laziness) - developers often prefer to concentrate on coding, rather than maintaining software (which in a way is fair enough. as long as their community is small enough). the only other reason i know of is licensing (when only the "owner" (copyright holder) of some piece of software can technically recompile/relink their software, and they cannot be bothered, eg because they already went out of business). this is one of the big reasons why so much software in the w32 world is exploitable and *stays* exploitable, even after severe bugs have been discovered... </rant> but i certainly don't want to start a flamewar on that topic :-) > libfaust dynamic version was added by Albert Graef (Albert can you remember > us your typical use case ?) and I use it sometime for testing purposes. ok. good to know. so for now, i'll *not* consider the dynamic libraries for inclusion in the Debian package. > libfaust API is C++ and C one, with some general entry points defined in > compile/generator/dsp_aux.hh, the LLVM backend in > compiler/generator/llvm/llvm-dsp.h and compiler/generator/llvm/llvm-c-dsp.h > as well as the Interpreter backend in > compiler/generator/interpreter/interpreter-dsp.h. This API is now considered > stable. Adding semantic versioning is certainly something we have to do… cool. though my question was targetted at the ABI (the application *binary* interface), which can change independently of the API. out of curiosity: do you think the libfaust-library + headers could be of general use outside of the faust compiler (and close relatives) itself? e.g. would having the libfaust-headers (+ libraries to link to) make any sense on a machine that does *not* have 'faust' installed? > And I see also that the public header are GPL, which is not what we want for > a library (I guess LGPL is what we should use). good idea. (though my remark in my last mail, about having to keep sources due to the GPL, does of course apply to the LGPL as well) gfmdsa IOhannes
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Faudiostream-devel mailing list Faudiostream-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/faudiostream-devel
