README: remove CMake section v1 PROPOSED

Stephen Gregoratto: 2
 README: remove CMake section
 README: Use fenced code blocks

 2 files changed, 19 insertions(+), 27 deletions(-)

[PATCH 1/2] README: remove CMake section Export this patch

---
 README.md | 16 ----------------
 1 file changed, 16 deletions(-)

diff --git a/README.md b/README.md
index 2983275..13ba137 100644
--- a/README.md
+++ b/README.md
@@ -88,22 +88,6 @@ flags like so:
     $ make
     $ sudo make install
 
-## compiling `pkgconf` and `libpkgconf` with CMake (usually for Windows)
-
-pkgconf is compiled using CMake on Windows.  In theory, you could also use CMake to build
-on UNIX, but this is not recommended at this time as it pkgconf is typically built much earlier
-than CMake.
-
-    $ mkdir build
-    $ cd build
-    $ cmake ..
-    $ make
-    $ sudo make install
-
-There are a few defines such as SYSTEM_LIBDIR, PKGCONFIGDIR and SYSTEM_INCLUDEDIR.
-However, on Windows, the default PKGCONFIGDIR value is usually overridden at runtime based
-on path relocation.
-
 ## pkg-config symlink
 
 If you want pkgconf to be used when you invoke `pkg-config`, you should install a
-- 
2.28.0

[PATCH 2/2] README: Use fenced code blocks Export this patch

---
 README.md | 30 +++++++++++++++++++-----------
 1 file changed, 19 insertions(+), 11 deletions(-)

diff --git a/README.md b/README.md
index 13ba137..c0a1642 100644
--- a/README.md
+++ b/README.md
@@ -23,7 +23,9 @@ environment variable.
 To set the environment variable on the bourne shell and clones (i.e. bash), you
 can run:
 
-    $ export PKG_CONFIG=/usr/bin/pkgconf
+```sh
+$ export PKG_CONFIG=/usr/bin/pkgconf
+```
 
 ## comparison of `pkgconf` and `pkg-config` dependency resolvers
 
@@ -72,21 +74,25 @@ rules will solve the problem.
 pkgconf is basically compiled the same way any other autotools-based project is
 compiled:
 
-    $ ./configure
-    $ make
-    $ sudo make install
+```sh
+$ ./configure
+$ make
+$ sudo make install
+```
 
 If you are installing pkgconf into a custom prefix, such as `/opt/pkgconf`, you will
 likely want to define the default system includedir and libdir for your toolchain.
 To do this, use the `--with-system-includedir` and `--with-system-libdir` configure
 flags like so:
 
-    $ ./configure \
-         --prefix=/opt/pkgconf \
-         --with-system-libdir=/lib:/usr/lib \
-         --with-system-includedir=/usr/include
-    $ make
-    $ sudo make install
+```sh
+$ ./configure \
+	--prefix=/opt/pkgconf \
+	--with-system-libdir=/lib:/usr/lib \
+	--with-system-includedir=/usr/include
+$ make
+$ sudo make install
+```
 
 ## pkg-config symlink
 
@@ -94,7 +100,9 @@ If you want pkgconf to be used when you invoke `pkg-config`, you should install
 symlink for this.  We do not do this for you, as we believe it is better for vendors
 to make this determination themselves.
 
-    $ ln -sf pkgconf /usr/bin/pkg-config
+```sh
+$ ln -sf pkgconf /usr/bin/pkg-config
+```
 
 ## release tarballs
 
-- 
2.28.0