Trouble "installing" PicoGK 1.7.5 or 1.7.0 via Visual Studio Code, ARM MacOS

[fudgtastic]

Hello,

I am aiming to install PicoGK on my arm-based MacOS computer.

I installed PicoGK following the instructions here: the /~https://github.com/leap71/PicoGK/blob/main/Documentation/Install_Mac.md

I have followed the instructions to set up VS code here: /~https://github.com/leap71/PicoGK/blob/main/Documentation/VisualStudioCode_FirstTime.md

and I have no issue getting through the "hello world" ConsoleApp1 steps. However, when I get to trying out the first PicoGK example, i get this error:

It seems like this is probably a known issue, given the main README file says the following:

So the best advice I am working from is "this should not happen". Though I have tried reinstalls of VS code, and tried PicoGK 1.7.5 multiple time and also 1.7.0, I am stuck and I would please like some help to proceed.

Thanks!

[LinKayser]

That is indeed weird. Could you share the PicoGK.log file — it's in your Documents folder.

We use Mac/ARM here and it works with our machines. So let's see if there's something about your config that is suspiciously different.

Best,
Lin

[fudgtastic]

Hi Lin,

I've uploaded the log file herein. Thank you for taking a look!

[
PicoGK.log
](url)

Regards,
Drummond

[EdwardChamberlain]

I also encountered this issue on ARM Mac trying to run the Example file.

Resolved by moving picogk.1.7.dylib from /usr/local/lib to bin\Debug\net8.0 within the example project.

[fudgtastic]

Bingo.

Thanks EdwardChamberlain!

[EdwardChamberlain]

Good to know it worked! I dont know enough about C# to have any idea what that works, but seems like picoGK is looking in the wrong place for the DLL.

You also have a demo that looks like the example images. Mine has a more jazzy reflective finish for some reason.

[LinKayser]

I is unclear why it doesn't work from the install location. If you put the dylib where you have it now, you have to put it there for every project and every configuration. Maybe Apple changed something in their default load path, will investigate, but a simple google search did not reveal any recent changes.
Lin