Correcting some errors and

also hoping these changes will
make things easier to read.
	modified:   README.md
	modified:   READMEcmake.md
	modified:   READMEwin-msys2.md

Author: davea42

README.md

@@ -196,9 +196,10 @@ For the full options list , do:
     /path/to/code/configure --help
 
 By default configure compiles and uses libdwarf.a.
-With `--enable-shared` appended to the configure step,
-both libdwarf.a and libdwarf.so
-are built and the runtimes built will reference libdwarf.so.
+With `--enable-shared --disable-sttic"
+appended to the configure step,
+libdwarf.so is built and the runtimes
+built will reference libdwarf.so.
 
 If you get a build failure that mentions
 something about test/ and missing .Po object files
@@ -210,12 +211,6 @@ necessary.
 See:
 https://www.gnu.org/savannah-checkouts/gnu/automake/history/automake-history.html#Dependency-Tracking-Evolution
 
-With 
-
-    --enable-shared --disable-static
-
-appended to the configure command
-libdwarf.so is built and used.  libdwarf.a is not built.
 
 Other options of possible interest:
 
@@ -227,27 +222,17 @@ Other options of possible interest:
 Sanity checking:
 
 gcc has some checks that can be done at runtime.
--fsanitize=undefined is turned on by --enable-sanitize
+-fsanitize=undefined is turned on  for
+configure by --enable-sanitize
 
 ### Options to meson on Windows (Msys2)
 
-All libdwarf builds are automatically shared object (dll)
-builds as of 0.8.0. 
-
-With
-
-    --default-library static
-
-on the meson command line
-one can build libdwarf as an archive and dwarfdump and the
-programs built will use the static library.
-
-The default is shared and can be explicitly
-chosen by:
+As of 0.8.0 meson builds default to be
+shared-library builds.
+the default can be explicity chosen with: 
 
     --default-library shared
 
-Has the same meson setup reporting as on Linux (above).
 
 ### Options to configure on Windows (Msys2)
 
@@ -257,6 +242,8 @@ If you need static libdwarf.a use meson or cmake.
 
 Has the same meson setup reporting as on Linux (above).
 
+See READMEwin-msys2.md
+
 ### Distributing via configure/autotools
 
 When ready to create a new source distribution do
@@ -266,6 +253,13 @@ a build and then
 
 # INCOMPATIBILITIES. Changes to interfaces
 
+### Comparing libdwarf-0.9.0 to libdwarf-0.8.0
+
+New interfaces allow full support for
+Mach-O (Apple) universal binaries:
+dwarf_init_path_a(), dwarf_init_path_dl_a(), and
+dwarf_get_universalbinary_count().
+
 ### Comparing libdwarf-0.8.0 to libdwarf-0.7.0
 
 The default build (with meson) is shared-library.

READMEcmake.md

@@ -1,6 +1,6 @@
 # Cmake on Unix/linux/MacOS/FreeBSD/OpenBSD
 Created 26 April 2019
-Updated 6 October 2023
+Updated 7 October 2023
 
 Consider switching entirely to meson for your build.
 
@@ -13,7 +13,12 @@ cmake builds a static library: libdwarf.a
 For cmake, ignore the autogen.sh
 script in the base source directory.
 
-By default cmake builds just libdwarf and dwarfdump.
+By default cmake builds just libdwarf and dwarfdump
+and libdwarf is a static (archive) library.
+To switch to a shared library output with cmake add
+the following to the cmake command:
+
+    -DBUILD_SHARED=YES -DBUILD_NON_SHARED=NO
 
 Lets assume the base directory of the the libdwarf source in a
 directory named 'code' inside the directory '/path/to/' Always

READMEwin-msys2.md

@@ -1,6 +1,6 @@
 #USING MSYS2 (WINDOWS) CMAKE, MESON, CONFIGURE
 
-Created 6 October 2023
+Created 7 October 2023
 
 msys2 provides an environment much like posix/unix/linux
 with programs precompiled for use on windows
@@ -17,34 +17,42 @@ library libdwarf.a is not supported. A static
 libdwarf.a can be built with meson or cmake.
 
 ### Shared library builds
-All libdwarf builds are automatically shared object (dll)
-builds as of 0.8.0.
+Libdwarf builds from configure
+and cmake  are static (archive) library builds
+by default.
+Meson builds to a shared library by default.
 
-With
+On msys2 with cmake one can generate a shared library
+build with: 
+
+    -DBUILD_SHARED=YEs -DBUILD_NON_SHARED=NO
 
-    --default-library static
 
-on the meson command line
+With the following on the meson command line
 one can build libdwarf as an archive and dwarfdump and the
 programs built will use the static library.
 
-The default is shared and can be explicitly
+    --default-library static
+
+
+The meson default is shared and can be explicitly
 chosen by:
 
     --default-library shared
 
-Has the same meson setup reporting as on Linux (above).
-
 configure will only allow generation of shared library
 builds, while for cmake and meson one can choose
-wither to build a shared library or an archive library
+whether to build a shared library or a static (archive) library
 (libdwarf.a).
 
+On msys2 with configure one gets a shared library build with:
+
+    --enable-shared --disable-static
 
 ### NOTE on linking against libdwarf.a
 
 If you are are linking code against a static 
-library libdwarf.a you must arrange to  define the
+library libdwarf.a you must arrange to define the
 macro LIBDWARF_STATIC in compiling your code that
 does a #include "libdwarf.h".
 
@@ -86,30 +94,27 @@ building and testing all the build mechanisms:
     pacman -S mingw-w64-x86_64-cmake
     pacnam -S mingw-w64-x86_64-python3-pip
 
-    To create a distribution
+    To create a distribution one needs xz:
     pacman -S mingw-w64-x86_64-xz
 
     to list packages
     pacman -Q 
     to remove packages
     pacman -R  <packagename>
 
-## cmake specific
+## Ninja speed
+
 cmake will generate ninja makefiles by default, add
 '-G "Unix Makefiles"' to the cmake command line to
 generate makefiles for gnu make, but we suggest you
 use "-G Ninja" for speed and clarity..
 
-Use
--DBUILD_SHARED:BOOL=TRUE  \
--DBUILD_NON_SHARED:BOOL=FALSE
-on the cmake command
-to be consistent with normal Windows use.
+## Set a Prefix for test installs
 
 To get a usable set of executables
 set a prefix (for cmake,
--DCMAKE_INSTALL_PREFIX=/c/msys64/usr),
-presuming  the bin directory
+-DCMAKE_INSTALL_PREFIX=$HOME/bin
+presuming the bin directory
 is something in your $PATH in msys2.
 Set an appropriate prefix whichever
 build tool you use.