Update NUCLEO_F401RE-device.mk

I updated this makefile to have the TARGETS_FOR_DEVICE exactly match
what I see in the mbed SDK Python build process.  I also updated to use
the same floating point flags as well.
Properly wrap main()

The mbed SDK expects the main() function to be wrapped so that it can
call mbed_sdk_init() and mbed_main() before calling the real main()
function.
Temporarily remove NUCLEO_F401RE support

The recent updates from revision 91 to revision 92 of the mbed SDK have
led to an issue where binaries are successfully built for this platform
but the resulting binary doesn't actually execute properly.  I will
revert this change once those issues have been figured out.
Merge branch 'working'

Updating to revision 92 of the mbed SDK.
Revert "Temporarily remove NUCLEO_F401RE support"

This reverts commit 6c96b73af64afe05693b72e02e04f0a6f1340483.

Re-enable NUCLEO_F401RE support in the working branch.
Added NUCLEO_F411RE option.

1. Tested with NUCLEO-F411RE board.
2. Tested samples : HelloWorld
Updated NUCLEO-F411RE makefile for new mbed SDK

The device specific makefiles now require a different format after the
latest mbed SDK and GCC4MBED updates.  I made the necessary changes in
this commit.
Force all object files from mbed.a to be linked

I have hit a few issues recently with the STM code base where weak
overrides weren't being pulled in because nothing was explicitly
causing the modules containing the strong implementations to be
pulled in.

The official solution for the STM devices is to explicitly list every
.o file in its HAL to the linker.

I am now using the --whole-archive linker flag to cause all .o files
found within mbed.a to be pulled in by the linker.  The section garbage
collector will still purge the unused code/data so it shouldn't lead
to code size increase except where it now pulls in the correct code and
didn't do so before.
Disable "Conflicting CPU architectures" link warnings

I added the --no-warn-mismatch linker flag to silence these warnings
which are generated when linking in the bare SoftDevice binary to
NRF51822 binaries.
Some cleanup to -whole-archive fix

I defined an all_objs_from_mbed() macro in gcc4mbed.mk and then call it
from the command list of the link rule in device-common.mk  This makes
it a bit clearer what is happening when you read the link rule.
Update installation notes for Windows

We no longer use cs-make but instead use a copy of GNU make.exe that
is found in the external\win32 sub-directory of the GCC4MBED
repository.
Merge remote-tracking branch 'upstream/master' into working
sync so I can merge device.mk s for STM