From e511c0d2a5d616081a7826416d111aff1d428025 Mon Sep 17 00:00:00 2001 From: Joshua Granick Date: Fri, 27 Feb 2015 11:00:58 -0800 Subject: [PATCH] Update README.md --- README.md | 27 ++------------------------- 1 file changed, 2 insertions(+), 25 deletions(-) diff --git a/README.md b/README.md index f8d1f79cb..7f6a86ec0 100644 --- a/README.md +++ b/README.md @@ -105,31 +105,8 @@ Lime currently supports the following targets: lime test mac lime test linux lime test neko + lime test android lime test html5 lime test flash -Native builds must be built on the same operating system as the target. As supported in Lime legacy, additional platforms (iOS, Android, BlackBerry, Tizen) will be restored in the near future. - - -Lime "Legacy" -============= - -OpenFL uses older Lime binaries, which are not used in the current version of Lime. These older binaries are derived from shared source within the NME repository, while the newer code has been rewritten to better suit the goals of the project. - -In order to rebuild Lime "legacy", you should follow the directions above for building from the source. You will also need additional dependencies: - - git clone https://github.com/haxenme/nme - git clone https://github.com/haxenme/nme-dev - git clone https://github.com/haxefoundation/hxcpp - - haxelib dev nme nme - haxelib dev nme-dev nme-dev - haxelib dev hxcpp hxcpp - - cd nme-dev/project - neko build.n - - lime rebuild hxcpp windows - lime rebuild windows -Dlegacy - -You can substitute "windows" for another available target. If you would like to use Lime from the source, but do not need to modify the content of the legacy binaries, it is much easier to download a current development build, and copy the "legacy" folder into your source checkout. Otherwise, the above steps should help. +Native builds must be built on the same operating system as the target. As supported in Lime legacy, additional platforms (iOS, BlackBerry) will be restored in the near future.