On Thursday, June 5, 2025 12:34:40 PM CEST Christian Schoenebeck wrote: > On Tuesday, June 3, 2025 8:53:36 PM CEST TJ Lindgren via Linuxsampler-devel > wrote: > > Has anyone tested Linuxsampler with a recent version of MacOS? I cannot > > get > > LinuxSampler working at all. Obviously, it’s not apple silicon but there > > are several issues preventing LinuxSampler from working it seems. > > > > - When loading the VST plugin, it is trying to open Fantasia as it does on > > Windows. However, Fantasia is using a very old version of Java that cannot > > run in MacOS so Fantasia cannot open. There used to be a workaround to use > > an older version of JavaApplicationStub, however the version used for > > Fantasia seems to be deprecated on recent versions of MacOS. > > > > > > > > - The AU plugin does not load at all. This includes versions previous to > > 2.4.0 as well as the most recent 2.4.0 release. > > > > > > > > - Both the VST and AU plugins do not scan correctly in several hosts. For > > example, the VST scans correctly in Reaper but not the AU. In Plogue > > Bidule, neither the VST or AU scan. In MainStage/Logic (AU support only) > > the AU does not scan. > > > > - QSampler requires libgig.10.dylib even though libgig.11.dylib was > > installed for previous versions (2.3.1) and libgig.12.dylib for the most > > recent version (2.4.0). So in order to open QSampler, you have to symlink > > the libgig file and rename it to libgig.10.dylib. > > Mja, confirmed. The Mac installer actually ships an ancient version of > QSampler and liblscp. This issue exists since the transition of liblscp/ > QSampler from autoconf to CMake. > > I guess the same applies to the Windows installer. > > The thing is, the binaries are automatically built on our server. Once they > are (re)built, they have to be installed into a specific directory on our > server for the Mac/Win installer scripts to grab them up. > > The problem I have is, I don't see an obvious way how to output where cmake > is installing to, or how exactly. I tried the only documented way which is > > cmake --install build --verbose > > But that does not output anything more than without --verbose.
OK, I checked with strace what cmake --install actually does: it does not install anything. It looks into a file ./build/install_manifest.txt, which is completely empty, then it stops. No idea why cmake generates an empty install_manifest.txt file. I just manually wrote some install shell commands for QSampler instead. I replaced the stable Mac installer link with the corrected Mac installer on the website. If I find some time I'll probably send a patch for cmake. Because honestly, now matter why that file is empty, IMO cmake should error out when a user tries "cmake --install" and cmake not installing anything. /Christian _______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel