first run in package location on osx yields can't find oF path what about projectgenerator

[danoli3]

@ofTheo yes I noticed now the current_path was /

(Re: changes in apple sandboxing of file locations.

fs::weakly_canonical(fs::current_path()); = /
ofFilePath::getAbsolutePathFS(fs::current_path(), false); = /

found a way around it
fs::path startPath = ofFilePath::getCurrentExeDirFS(); = real path where I then ran from paths upwards to parent folders

[danoli3]

I think this is occurring randomly due to projectGenerator living at openFrameworks/projectGenerator.app/Contents/MacOS/projectGenerator

so its checking code for ../../ or ../../../ is not working. Adding dynamic up folder check

[ofTheo]

This is App Translocation which is a security feature of macOS.
It gives the app a randomized runtime directory until you move it manually in the Finder.

We've tried a ton of things to break App Translocation but nothing works well.
I even tried a signed DMG for the whole OF package but it didn't solve it.

So the above message is normal ( but I should note is designed for people using the whole OF package ), so as soon as you move it into OF_FOLDER/projectGenerator/ the message should go away and it will see the OF path.

Feel free to close the issue if that's it.

[danoli3]

Fixed with auto finder oF code up folder parents.
ofPath is found by directory level of sub folders: addons / libs / scripts
prior was just sub folder "scripts" ?

[ofTheo]

Ah sweet! Nice approach 😁