Oh, yes.
And I am using a copy file step to move the lib into the right place.
If I drop the old dylib into the project it all comes to life - so I know all other things are equal. Im sure its something in the XCode build settings, but Im not familiar enough to say what.
Are change notes on the library available where you might figure out what’s going wrong?
I know one of the things that can go wrong is the paths to dependencies, I’m not sure how to explain it. There was a lot of googling and advice involved with getting the OpenSSL library to play friendly within an app.
This article is a huge technical insight into fixing iPhoto et all for Catalina, but has a major portion about dylib stuff. Jump down to Step 2 / name_tool for where I started with OpenSSL.
Edit: It covers extracting the dylib and changing the path, which is what I needed. It’s not super detailed on what’s actually going on, I must have read about that elsewhere.
Seems like we got it fixed for @Chris Halford with using SoftDeclareMBS to load a dependency first:
[code]Dim f As FolderItem = app.ExecutableFile.parent.Child(“libOther.dylib”)
Dim s2 As New SoftDeclareMBS
If s2.LoadDylib(f.NativePath) Then
MsgBox “OK”
Else
MsgBox s2.Liberror
End If
Soft Declare Function testFunction Lib MyLib ( s As cString) As Integer
Dim h As Integer = testFunction( “test” )
If h <> 0 Then
MsgBox "Success "+str(h)
Else
MsgBox “Failed”
End If[/code]
So when loading the second lib, there is already the first one loaded and initialized and it works.