Dan Rosser
Dan Rosser
I think its due to Debug Mode on default build, try release
I think its actually macOS target folders should be fixed with permissions and or chmod
@dimitre it means it not signed and you just gotta run the build script to sign it ```scripts/osx/build_cmdline.sh``` Issue is macOS permissions now are hectic for unsigned code
Building from Xcode will make the file correctly, but it's linking against the mach-o of the files in the .app: invalidating the cmdLine.exe that is copied out of that .app...
not a libs problem, was a new macOS permissions problem
> it would be great if PG could be built in the future only as a commandLine application instead of an app bundle. scripts/osx/build_cmdline.sh
its copying to the temp folder which is also the bin folder, I had a solution for this at one point, was something to do with changing the cache dir
This is happening regardless of xcframeworks or .a binding or libs, it’s a thing with temp static location shouldn’t be an issue once we just set the path correct. Normally...
Yeah misconfiguration of projectGenerator it seems. Manually adding to LDFlags causing this
Yeah this is all due to misconfiguration of ``` [CONFIGURATION](https://developer.apple.com/documentation/xcode/build-settings-reference#CONFIGURATION) Setting name: CONFIGURATION Identifies the build configuration, such as Debug or Release, that the target uses to generate the product....