I'd be very appreciative of any help I can get with compiling Rubber Band Library on Windows. I'm a noob.
I first started off with trying to get it to compile using Visual Studio. I felt I was going nowhere, so I scrapped that effort. I was able to compile libsamplerate (SRC) this way, so I initially went with the same approach.
Then, I went to cygwin. Right now, I'm stuck during ./configure at:
"checking for SRC... configure: error: Package requirements (samplerate) were not met: No package 'samplerate' found"
Looking at config.log, it appears that pkg-config is looking for samplerate.pc. I know nothing about linux, but isn't this something that only exists on linux platforms? I mean, I have the libsamplerate.dll ready, but it seems like I need to provide the source plus the C++ and linker flags.
Will I run into similar problems with FFTW3, Vamp, LADSPA, etc..? With my limited knowledge, this seems like a nightmare.
So, my questions are: is there a better way to do this? The windows executables are already being provided; can you share build instructions / hints? or better yet, can you provide a Windows DLL? I'm really only interested in using the library, so if I could abstract away all this other stuff, it would make life easier. Plus, RBL may see more adoption if Windows users had easier access to it :)
Thanks for the note, and I'm sorry you've been having troubles. I appreciate that it's not the simplest thing to get the Rubber Band Library to build on Windows. The GPL edition does not actually contain support for MSVC at all (though the commercial edition does) and some Makefile tweaking is necessary for a Cygwin or MinGW build.
We're quite keen not to provide binary libraries for any platform, for the free edition, partly because we don't want to get into all the complications arising from compatibility and dependency issues for a C++ library (which compiler binary interface? which runtime? etc). However, it does seem like it would be sensible for us to provide a minimal Cygwin-ized Makefile for people doing builds using the GNU tools on Windows... maybe that would be a good idea for the next release.
In the mean time, what I might suggest would be to ignore the configure step, if it doesn't produce sensible results for you straight away, and instead copy Makefile.in to Makefile and edit it to add the necessary paths by hand. Look for any keywords in the Makefile that begin and end with an "@" character, and either replace them with the necessary paths, or delete them. If you only want to build the library, you can simply delete any paths related to Vamp, LADSPA, or libsndfile -- but you will still need to have an FFTW build ready, and to have correct paths for that.