> On Sep 9, 2016, at 1:09 PM, Jason Boyd <[email protected]> wrote: > > I realize it is documented that building crosswalk apps from OS X is not > yet documented, but since the crosswalk-app-tools README claims OS X is > supported, I am wondering what if anything I have not set up to do this. > > Packaging Crosswalk apps for macOS is not supported. Crosswalk does not > run on macOS. >
I'm not packaging for macOS. I'm trying to build *from* mac OS X. > Packaging Crosswalk apps for Android on macOS should work though it’s not > intensively tested. > "Not supported" and "should work" are nebulous, I'm trying to understand which part is not yet supported. > I get an error when doing crosswalk-pkg, details below. I am hoping for at > least an explanation as to what might be broken, if not a solution, as I am > trying to determine how feasible it will be to have OS X build setup while > targeting Android devices. > > Any help is appreciated. > > From the output you can see : > > *** ERROR: Checking for lzma… null > > have you tried to install it? > The docs online say to ignore this error. I don't think it's the issue. Troubleshooting, it looks like the prob may have to do with the tool trying to copy every file in my existing project to the archive, and barfing because it's too large. I'm trying to research how I would tell it not to copy all files, e.g. adding to some aapt.android.ignore property, but the docs don't help. Actually I'm quite confused from the docs about when to do crosswalk-app create vs crosswalk-app build vs crosswalk-pkg. If all these commands end up generating the entire Android project, what is the implied workflow? Where do any persistent config settings go for the build app?
_______________________________________________ Crosswalk-help mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
