Unable to find libncurses.6.dylib when launching Hise + Faust
-
I've successfully build Hise with Faust, however Hise crashes with this message:
I'm running MacOS 13.0.1 on a M1Termination Reason: Namespace DYLD, Code 1 Library missing Library not loaded: /opt/local/lib/libncurses.6.dylib Referenced from: <E0F3F783-5955-3BDF-BB3D-2B65F065749D> /Users/USER/Music/*/libfaust.2.54.9.dylib Reason: tried: '/opt/local/lib/libncurses.6.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/opt/local/lib/libncurses.6.dylib' (no such file), '/opt/local/lib/libncurses.6.dylib' (no such file), '/usr/local/lib/libncurses.6.dylib' (no such file), '/usr/lib/libncurses.6.dylib' (no such file, not in dyld cache) (terminated at launch; ignore backtrace)
-
@ulrik So I installed libncurses with brew but still no luck finding that lib
-
@ulrik this is the Faust file I downloaded and installed in the tools/faust folder like this
Faust-2.54.9-x64.dmg
-
@ulrik I installed ncurses with mac ports and Faust will find the lib :)
but, it complains about ncurses not being x86_64, I thought it was universal?Any thoughts?
(mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64')),
-
@ulrik Ok solved, I had to install ncurses +universal
Using Macports I installed the library using:
sudo port install ncurses +universal
and now Hise is up running :)
I didn't know you had to install other libraries to run Faust, maybe it's a good idea to make a note of that in the documentation?
-
@ulrik
You are the only one here who asks questions here and then answers them straight away - amazing - Happy New Year Ulrik. :-) -
@MikeB Haha, yes sometimes talking to yourself will give you the right answers :)
Happy new year to you Mike -
-
@Christoph-Hart I'm using MacOS Ventura 13.0.1 (22A400)
and Faust-2.54.9-x64 -
@ulrik I'm following the helpful video by Tania here:
https://forum.hise.audio/topic/7021/faust-hise-video-tutorials-hny-2023and I get an error when Hise try to find the "stdfaust.lib"
-
@ulrik you need to set the FaustPath in the macOS settings. Also check the sticky post with the build instructions.
-
@Christoph-Hart Ok, I'll take a look, thanks!
-
@Christoph-Hart Ok, I've set the Faust path but now Hise crash every time I create a new dsp file and load it
This is my journey:- No problems building Hise with Faust enabled
- Launching Hise after successful build result ina message saying "libfaust.2.........dylib can not be opened because its identity is not confirmed"
So I use the terminal to make it trustworthy
xattr -cr /Users/ulrikboden/Music/Hise/HISE-develop/tools/faust/lib/libfaust.2.54.9.dylib
This will make Hise open, I set the path to Faust in the settings
and start exploring this exciting new world of Faust :)
I create the dsp Network file and load the "core.faust"
however it ends abruptly when I create a "New File" in core.faust, Hise crashing.
So I open the project again, (the "New file" I created in core.faust is there, I just need to load it, but as soon as I try Hise crash again.
If I open the created .dsp file in an external editor it says:
// Faust Source File: CompressorST // Created with HISE on 2023-01-02 import("stdfaust.lib"); process = _, _;
and that looks good, right?
and this is my network file
<?xml version="1.0" encoding="UTF-8"?> <Network ID="STCompressor" Version="0.0.0"> <Node FactoryPath="container.chain" ID="STCompressor" Bypassed="0"> <Nodes> <Node ID="faust" FactoryPath="core.faust" Bypassed="0"> <Properties> <Property ID="ClassId" Value=""/> <Property ID="NumParameters" Value="0"/> </Properties> <Parameters/> <SwitchTargets/> </Node> </Nodes> <Parameters/> </Node> </Network>
What am I doing wrong?
-
/opt/local/lib/libncurses.6.dylib : yes I recently realized that our recent Faust binary packages have several /opt/local/lib/xxx dependancies (because we build them using a MacPorts installed LLVM version), which is bad :anguished_face: . But embedding LLVM without any dependancies is not so easy. Still fighting to find a proper solution.
-
@Christoph-Hart Here is Chat GPT answer !
How to build LLVM on macOS without any dependancies ?
To build LLVM on macOS without any dependencies, you will need to build the LLVM source code from scratch. This process involves downloading the LLVM source code, configuring the build environment, and compiling the source code using a suitable compiler.
Here are the general steps you will need to follow to build LLVM on macOS without any dependencies:
Download the LLVM source code. You can obtain the latest stable release of LLVM from the LLVM website (https://llvm.org/releases/), or you can check out the latest development version of LLVM from the LLVM Git repository (https://github.com/llvm/llvm-project).
Configure the build environment. LLVM uses the CMake build system, which requires you to specify a number of build options and configuration variables. You will need to create a build directory and run CMake to generate the build files for LLVM.
Compile the source code. Once the build files have been generated, you can use a suitable compiler (such as Clang or GCC) to compile the LLVM source code. You can use the make command to build LLVM, or you can use a build tool such as Ninja to build LLVM more quickly.
Install LLVM. Once the LLVM source code has been compiled, you will need to install it on your system. You can do this by running the make install command from the build directory.Note that building LLVM from scratch can be a complex process, and it may require a significant amount of time and resources. If you are not familiar with building software from source code, you may want to consider using a pre-built version of LLVM instead. This will allow you to use LLVM without the need to build it yourself.
-
Same issue here. Monterey - M1 - Xcode 13.1
-
@sletz
Is it possible to get hands on an older Faust binary package?
It was... -
@ulrik Ok, I installed older Faust binaries "Faust-2.50.6-x64" and I have no more crashes :)
I still have to use the "xattr -cr /path to the libfaust.dylib, but that's a Mac thing....
-
What was the crash? Any crash log?
-
@sletz sorry for late answer, no crash logs I'm afraid