Fixes 'block hotkey enable'
(Android) Build fix
Set savestate_auto_load to false by default - certain cores still
crash with this feature on so we don't want to leave this enabled
by default
Split up some of the code in retroarch.c to general.c
Minor cleanups in retroarch.c
Indent/style nits
Refactor do_state_checks - returns false if paused
(config_file.c) Change some control code flow
(Lakka) Make settings values responsives
(Lakka) Move tweening related functions in an external lib

so they can be used from another menu driver. Also add more tweening functions.
Merge pull request #1038 from lakkatv/lakka

(Lakka) Move tweening related functions in an external lib
Split up check_movie_record into check_movie_init and check_movie_record
Refactor check_movie_record code some more
Refactor check_enter_menu
Add tween.c to griffin.c
Move this to the bottom for consistency with the other null drivers.
Merge branch 'master' of github.com:libretro/RetroArch
(Apple) iOS Xcode 6 build fix
iOS: Directly synthsize RAMenuItemBasic properties

On iOS, when properties are not explicitly synthesized in their implementation, the compiler will attempt to do something that is called "autosynthesis", which is essentially it synthesizing the properties for you. However this problem with this is that it can trip up the compiler if you have a subclass of a base class that has a property with the same name as one in the base class.

Also consider how properties work. Say we have a property like so:

@property int someVar;

This is telling the compiler to make a getter and a setter for a class member variable named someVar which is of type int. So the following functions will be created.
+(int) someVar(), which is the getter.
+(void) setSomeVar:(int) var, which is the setter.

In this case, RAMenuItemBasic inherits from NSObject, which already has a function named "description", yet we were trying to generate a getter/setter for our own variable named that, which leads to clashing. This is why the property was never being synthesized correctly. Directly declaring the synthesizing calls ourself fixes this.
Merge pull request #1040 from lioncash/ios-fix

iOS: Directly synthsize RAMenuItemBasic properties