Previously, the value was "iphone-11". Now the regex is ~/iphone-\d+/g
As long as the naming scheme stays the same, this should choose the newest iPhone supported by Xcode, and we won't need to update manually anymore, like in commit 72dd60f1c8
Fixes error: The armv7 architecture is deprecated. You should update your ARCHS build setting to remove the armv7 architecture. (in target 'Build Haxe' from project 'MyProject')
Using `userAgent` to tell whether the app is running on Android. This isn't foolproof, but will work more often than the previous approach (where you chose at compile time and your choice applied to all devices). Resolves#1655.
`substr(7)` returns the substring _starting_ at character 7, which will never be "windows". The author meant to type `substr(0, 7)` instead, to get the substring ending at 7.
We could easily make this change, but given that the code has been successfully using forward slashes for several years, I prefer to simplify.
Nowadays you're supposed to omit this type declaration, but what I didn't realize is that that feature was added in Haxe 4.1. Since Lime still needs to support earlier versions, we'll just have to do it the old way.
This message comes up relatively often when a new user tries to set up Lime, but fails to give any instructions a new user could use.
This commit adds a new message explaining the most common issue and how to solve it. It also provides file paths, which may help with more in-depth debugging.
Plus, do some cleanup. For instance, `nekoOutput` is only used in one
spot, so might as well declare it there.
Aside: I doubt `fullPath()` is needed, but I don't care to test it.
The no-inline macro was added previously to fix a compatibility issue with an older version of Haxe. It remains to be seen whether or not it is necessary as it seems to create conflicts with intermittent versions of Haxe. For this purpose we will remove it, unless it is deemed necessary again in the future. See: https://github.com/openfl/lime/discussions/1645 for more info.
* Apply markdownlint's recommendations.
It's not a fan of double blank lines.
* Fix accidental HTML tag.
The tag doesn't get rendered, and it looks like the line says "Fixed
merging of multiple tags in project files." Which makes perfect sense at
a glance, so it isn't surprising this wasn't noticed.
Thanks to markdownlint for catching this. Now that all its minor
warnings are gone, important ones will stand out.
* Write first pass of 8.0.1 changelog.
Includes commits up to Jan 11, 2023.
* Escape underscores.
* Add release date
---------
Co-authored-by: Josh Tynjala <joshtynjala@bowlerhat.dev>
