Should Lua be vendored like it is?

[colindean]

I found this framework bundle that might be a more idomatic way to ship it.

[colindean]

Ideally, it’d be nice to keep it in a submodule or otherwise included as a dependency of some kind. I’m very, very new to Cocoa development, so I don’t know how best it’s done in this ecosystem.

In the Ruby world, we’d specify the dependency in a bundler Gemfile, then vendor the gem when shipping. Similarly, in a Maven project for Java or Scala, a dependency is cached locally and then included in the shipped jar file or directory with a gaggle of jar files.

What is done in the Cocoa toolset? I heard of CocoaPods, but I don’t know a whole lot about it.

http://cocoapods.org/?q=lua

[colindean]

From that, there's also this, but I think you've already integrated with Lua itself, rather than using a bridge:

https://github.com/PedestrianSean/ObjC-Lua

[jasonm23]

CocoaPods analog to a Gemfile would be Podfile, however, that would rely on the Lua framework being packaged with a Podspec and available on CocoaPods registry.

Which apparently seems likely: http://cocoapods.org/?q=lua

[colindean]

Seems that perhaps that Lua.framework package I linked to might be ripe for some fixin’...

[colindean]

Fair enough.

On June 21, 2014 6:25:07 AM EDT, Steven Degutis notifications@github.com wrote:

@colindean We use Clojure and Ruby at work, and I do love the
dead-simple dependency management that Leiningen and Bundler give me. I
haven't really gotten into CocoaPods yet, since I started doing Mac
apps about 5 years ago before it came out. Back then, the simplest way
was to throw the source code right into your project. It still is the
simplest way actually, although it's definitely got some drawbacks. But
I think the pros outweigh the cons in this situation. We don't have
such a large dependency tree that makes it worth using a third party
system. Lua stands on its own. And when we need to upgrade Lua, it
would be pretty easy. So at this point I don't see much benefit to
using CocoaPods or Lua.framework or even building liblia.a and
statically linking against that.

---

Reply to this email directly or view it on GitHub:
#22 (comment)

[colindean]

Just to add a comment in case anyone revisits this...

The author of Lua.framework has some builds available here and is looking into why it doesn't compile at the moment here: derkyjadex/Lua-Framework#1.