But why?
I intentionally ignored making it work on MacOS. Otherwise, it will package successfully only to crash when you deploy it.
Lambda runs on Linux. The binaries you package on MacOS will never work.
Is there a use case that I'm missing?

this is why working at night is not good..)
So we don't have linux as daily using machine, mbe add cross compilation or may be add container?
My point is to have less setup and get it working on osx

I have a couple of docker images that I use for CI.

See if you can improve on those to streamline the process?!
Cross-compilation can be tricky, and there's already a learning curve to C++ on Lambda. I'd rather stay away from that.
That being said, I don't want to shut the door on that option. It might a productivity boon if it's done right.

So, I guess my answer is, see what you can come up with :)
I'm happy to review it.

You might find https://github.com/daleobrien/aws-lambda-cpp-hello-world could help. It will build a "hello world" lambda function on OSX using only docker and produce a zip file you can then use.