Continuing to try and simplify the build system, calculate the remaining
two autoconf variables from the existing config.mak.
For the moment, leave a configure and configure.ac file in place to
allow any old build systems to continue to function without errors.
By switching to the "any" architecture, we no longer need to template
the debian/control file. This simply claims that the package can be
built on any known debian arch - which we currently think is true - so
it will help future portability.
This may impact builds on Debian 8, but that version has been out of
support for over three years. I didnt test it, but since using this
helper is the preferred method it may actually help builds on older
versions.
When building on win32 systems, simply add the win32 specific functions
to the libn2n.a, which simplifies the commands needed.
By moving the win32 source code into the src directory, the source code
is better consolidated.
If there is a way to turn off the mingw insistence that it will rewrite
the filename it was given in the "-o" options, I have not been able to
find it. I could easily handle all the moves or renames at the end of
the build process if I could turn off this feature. Especially since it
means that make often thinks that the file has not been built (the
filename that make knows about is not the file that actually gets built
by the mingw gcc, so the if-newer tests that make applies will always
fail)
It looks to me that the correct way to address this build wrinkle is
simply to add the win32 functions to the libn2n when building a win32
output, then there is no additional magic library juggling required for
the win32 case
There is a minor change - after this, the macos man pages are also
installed into the /usr/local PREFIX. This seems like the correct
location to me.
Longer term, the usual autotools process of installing everything into
/usr/local should be used. Files installed in /usr should be done by
a package management tool, so this default makes sense to use.
