SPM and Workspace builds need to be added to the XCode portgroup - it's something that I've been working on for a while.
I'm a little surprised the sandbox is involved at all. Is it XCode's sandbox complaining? Or is it Terminal? Make sure the terminal has full disk access. —Mark _______________________ Mark E. Anderson <m...@macports.org> MacPorts Trac WikiPage <https://trac.macports.org/wiki/mark> GitHub Profile <https://github.com/markemer> On Fri, Dec 10, 2021 at 7:57 AM Andrew Udvare <audv...@gmail.com> wrote: > I am testing out how to build Xcode-based packages that use Swift > Package Manager (SPM) and it seems even with 'hacks' to make Xcode not > do any downloading of code, there's still some network activity (or > something the sandbox is blocking) that I have not figured out. > > Example port: https://github.com/Tatsh/ports/tree/master/aqua/eul > > Try using this with `port -d destroot` to see everything. You will get > this error: > > Resolve Package Graph > > sandbox-exec: sandbox_apply: Operation not permitted > > sandbox-exec: sandbox_apply: Operation not permitted > > sandbox-exec: sandbox_apply: Operation not permitted > > sandbox-exec: sandbox_apply: Operation not permitted > > cannot update Package.resolved file because automatic resolution is > disabledxcodebuild: error: Could not resolve package dependencies: > sandbox-exec: sandbox_apply: Operation not permitted > sandbox-exec: sandbox_apply: Operation not permitted > sandbox-exec: sandbox_apply: Operation not permitted > sandbox-exec: sandbox_apply: Operation not permitted > cannot update Package.resolved file because automatic resolution is > disabled > fatalError > > Thoughts on how this can be worked around? If anyone figures out what > these blocked operations were I'd be very interested in knowing. > > Thanks > Andrew >
