Maybe this will help you. I have a "zero dependencies" fork of fluidsynth in single header format. But it is not full, only synth and player modules, all the rest was removed. It is also based on an older version, I haven't merged with latest version.
https://github.com/rpvelloso/fluidsynth Em sáb, 14 de mar de 2020 13:01, <fluid-dev-requ...@nongnu.org> escreveu: > Send fluid-dev mailing list submissions to > fluid-dev@nongnu.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.nongnu.org/mailman/listinfo/fluid-dev > or, via email, send a message with subject or body 'help' to > fluid-dev-requ...@nongnu.org > > You can reach the person managing the list at > fluid-dev-ow...@nongnu.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of fluid-dev digest..." > > > Today's Topics: > > 1. Re: Building libfluidsynth to include in python package (Tom M.) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 14 Mar 2020 08:53:56 +0100 > From: "Tom M." <tom.m...@googlemail.com> > To: Marc Evanstein <m...@marcevanstein.com> > Cc: FluidSynth mailing list <fluid-dev@nongnu.org> > Subject: Re: [fluid-dev] Building libfluidsynth to include in python > package > Message-ID: > <CADHnbai4ttaTESfHCuNzuEtfoRYYvW8CbdpDeyH2=THJoe= > g...@mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Marc, please make sure to include the mailing list when replying. > > On 3/13/2020 7:43 PM - Marc Evanstein wrote: > > > > Hi Tom -- thanks for your response. > > > > I'm a little unclear: how would I produce something like the prebuilt > > windows binaries that you linked to when building from source? (The > > process of building from source has always been a bit mysterious to me.) > > I followed the instructions at > > https://github.com/FluidSynth/fluidsynth/wiki/BuildingWithCMake, and I > > seem to have done all the steps successfully (installing the > > dependencies, running cmake, running make), but "make install" just > > seems to install it in the system, right? How do I make a standalone > > package? > > > > Thanks, > > > > Marc > > The term "standalone" is technically not correct. The binaries that > you build will always have operating system specific dependencies > (e.g. the kernel, the standard C library, socket/networking libs). > That's why I said you need to build fluidsynth on all platforms and > architectures that you plan to support. After each "make" step you put > the libfluidsynth in a zip file (or whatever you plan for > distributing). Additionally, you may include some libraries that > fluidsynth depends on in that zip as well. Most notably: glib. Finding > a good compromise which dependency libraries to bundle and which not > is difficult. To see all the libraries that fluidsynth depends on you > may use the dependency walker on windows. On Linux you may simply > execute ldd libfluidsynth.so > > make install installs fluidsynth to the system, yes, so you don't need > that step. > > Tom > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > fluid-dev mailing list > fluid-dev@nongnu.org > https://lists.nongnu.org/mailman/listinfo/fluid-dev > > > ------------------------------ > > End of fluid-dev Digest, Vol 200, Issue 5 > ***************************************** >
_______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
