allow LDFLAGS to be set by user

Move old LDFLAGS variable to LDLIBS. By doing ths, a user can set their
own LDFLAGS without breaking the build. A case in which this can be
useful is hardening with debian, e.g.

    $ dpkg-buildflags --get LDFLAGS
    -Wl,-z,relro
allow AESNI to be disabled
Allow setting the LIBDIR at build time
easier static builds (STATIC=yes)

This will also disable AESNI
Revert "fixed typo" and "fixed crash for Windows"

This reverts commits c8a80a497d6b7f0f98841b72febb0dba9fabec28 and f7791e5289ef61860e0fca024f86c31e448982f1

This didn't actually fix Windows crash problem. In fact, it still
crashed without --log=0 being set. Changes to the i2pd.vcxproj file
fixed the crashes with VS 2013 > update 1.  i2pd now works with VS 2013
Update 3 and Update 4 RC.

Since these changes didn't have the intended effect, let's remove them.
Various changes to Windows build

- No hard coded dependency paths. These are better set with environment
  variables or property pages.
- Don't require admin rights to run
- Add support for running on Windows XP (note that Boost and Crypto++
  *also* need to be built targetting XP).
- Explicitly set type to console application
- Initial stubs for building x64 version
- Turn off sending error reports to Microsoft
- spaces, not tabs (matches the default when saved by VS2013 itself)
- disable multibyte
- re-enable SDL checks
update vcxproj.filters
minor updates to readme

* grammar fixes
* note working VS2013 version
* change tabs to spaces to ensure proper viewing on systems with
* different tab settings
updates to innosetup script

* support installation of both x64 and x86 binaries
* add readme
* add function to convert line endings. The README.md file currently has
  Windows line endings, but if that ever changes this function will
  automatically make the file "Windows friendly".
innosetup: Add i2pd to PATH
Adding Windows build instructions
Merge branch 'master' into proposed_build_fixes

Conflicts:
	Win32/i2pd.vcxproj