You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 20, 2020. It is now read-only.
LuaDist allows me to embed a package manager and Lua into a node js project (for fun), great, no global dependencies! But im on mac os and cmake is not natively available. That and in the node community it is frowned upon to ask for a user to install something like cmake to get the project to work, it should just work, I don't want the user to know about Lua at all.
My solution is to embed cmake into my application using a neat script and then rewire the initial luadist install script. this work well for getting the _bootstrap repo, It even gets through 90% of the install, but then I hit a snag. cmake is searched for from path.
Is there:
A, a variable to change the location of cmake in luadist-git
B, a way to build without cmake
C, have you considered embedding your build dependencies?
Thank.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
LuaDist allows me to embed a package manager and Lua into a node js project (for fun), great, no global dependencies! But im on mac os and cmake is not natively available. That and in the node community it is frowned upon to ask for a user to install something like cmake to get the project to work, it should just work, I don't want the user to know about Lua at all.
My solution is to embed cmake into my application using a neat script and then rewire the initial luadist install script. this work well for getting the _bootstrap repo, It even gets through 90% of the install, but then I hit a snag. cmake is searched for from path.
Is there:
A, a variable to change the location of cmake in luadist-git
B, a way to build without cmake
C, have you considered embedding your build dependencies?
Thank.
The text was updated successfully, but these errors were encountered: