Buoy questions

Buoy
1

I did not want to litter your release thread more.

So I was trying to “puncture first hole through” with a simple test in talking to Dylib.

error: cannot find library ‘libTestLibrary.dylib’ for Declare (looked for /Applications/Buoy/lib/stubs/arm64-apple-macos/libTestLibrary.dylib.tbd,

I did not know where to put the dylib. Then I got error which gave me hint to maybe put it in the lib/stubs.

Then I put it in the lib/stubs but I still get error as shown above. it seems to want tbd and not dylib ? i do not know what that is or how to make it, or where the dylib goes then).

Thanks.

2

This is a package?

you shouldn’t need to put anything in the buoy libs folder. That’s strictly for buoy itself.

3

Ah, its just dylib with one function that I made, with intent to then declare into it, like this:

Declare Function CalculateSomething Lib “libTestLibrary.dylib” Alias “CalculateSomething” (a as Int32, b as Int32) As Int32

So its just first try to contact to see if I can later make full component.

But it does not find the dylib

4

Ah. I was working on this Saturday. There’s something up with @rpath that’s causing this behavior. I’ll have to look at it when I’m not at work.

please file a bug report at:

5

There is no rush I am just testing things

6

I just noticed also that it has your own user hard coded in there somewhere:

error: cannot find library ‘libTestLibrary.dylib’ for Declare (looked for /Applications/Buoy/lib/stubs/arm64-apple-macos/libTestLibrary.dylib.tbd, /Applications/Buoy/lib/runtime/arm64-apple-macos/liblibTestLibrary.dylib.dylib, and /Users/gregolon/Work/Git/buoy/build/runtime/liblibTestLibrary.dylib.dylib)

7

That’s so y’all will know who I am!

8

So you just made a dylib and a declare with no path info. Try ./lib name.dylib

9

I actually managed to get it to work enough to test a bit.

I had to put the dylib into lib/runtime/arm64-apple-macos

Which is good enough to test, maybe not the future of things when you have thought of a component format.

Also in the declare I had to call it “TestLibrary” instead of “libTestLibrary” since your framework I presume seems to auto add lib into it.

And then it all worked.

Thanks

10

Without having tested a lot then first impressions is that component format could maybe be just directory

with small Buoy stub then all the platform directories for the dylibs. So if someone wanted to use the component they would just put the component directory at same place as their project.

(is just idea from the little I know at this moment)

11

Haha yes we all know that. And it is impressive what you are showing here. Bad for XoJo that you are gone. Maximum know how. No question. Somehow I would try to hold you in the environment how ever I could assist that. But hey, now you present a new basic with llvm and more. That’s pretty interesting. I hope that it will be one day open sourced so I can have a look how you handled the comiler.

12

Did you try putting ./ in front of the dylib name in the lib string?

13

That does not work it creates even more strange path.

image

Only thing that works is to have the library actually be called libxxx, and call it by xxx (currently).

With that said I still got the first lib I made to test working and can update it but cannot make 2nd one, I have not pinpointed exactly why yet though. There is definitely some difficulty with the paths currently, I may have copied the first one also somewhere at first which is maybe why 2nd one wont work, we will see.

14

I personally hope he finds model where he can live on it. (closed or open source is not super important). If someone can live on a thing like this then it will thrive and not die out.

15

Clearly the search tree is not set up for just row dylibs placed with an app. It was working a month ago but that was before I started work on packages and I must’ve screwed with that somehow.

16

Its not big deal, I can find out what did differently in the first test and use that method to test porting significant component for now.

17

Yeah I found what I did. Originally when I was doing declares it was just for console apps and linking to “whatever you find next to the app” was just fine. When I did the packaging work, that got accidentally dropped. What I’ll do is add an option to the compiler that lets you specify libs to link.

18

it’s pretty simple actually. It’s a cross-platform compiler built around LLVM and lld consumed as libraries — no spawned clang / ld subprocess.

It does mean that I have to vendor LLVM though and that in of itself was a huge challenge. I’ve had a few run-ins with the different optimization modes (they’re all exposed BTW) where using one mode or another ends up generating a bad binary. I suspect that’s the reason that Xojo kept having to shift in the beginning… but I’m striving to keep all of the optimization levels available, to the best of my ability. we’ll see.

When I’ve had enough language development, I’ll take a stab at doing a debugger for VSCode in LLDB along with a debugger stub.

19

Like I said, good job. Llvm is hard stuff. Not the simplest. It will be hard work until the end of the process but…

20

Is class not supported in a Namespace ?

I get error if I put anything else than a function in a namespace.