Closed sebsto closed 5 months ago
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
Can one of the admins verify this patch?
somewhat replaced by https://github.com/swift-server/swift-aws-lambda-runtime/pull/292
closing in inactive PRs, feel free to re-open if still relevant
I propose to re-arrange the file and package structure in
Examples/LocalDebugging
to make it work with thearchive
plugin.Motivation:
The current directory and package structure in the
Examples/LocalDebugging
example does not work out of the box with thearchive
plugin. See https://github.com/swift-server/swift-aws-lambda-runtime/issues/276Modifications:
I re-arranged the package structure to share the same
Package.swift
for the targetsMyLambda
andShared
. This allows the plugin to build and archive MyLamba. I also made minimum changes to the Xcode workspace to continue to be able to build and debug from Xcode.Let me know if there is a better way to arrange package and file in this project to work with : Xcode builds, command line builds, and the
archive
plugin.Result:
Project now builds with
swift build
It runs withexport LOCAL_LAMBDA_SERVER_ENABLED=true && swift run MyLambda
. It packages withswift package --disable-sandbox archive
It runs by selecting theMyLambda
target in Xcode It runs by selecting theMyApp
target in Xcode