Remove manual Make instructions from docs

Author: milancurcic

README.md

@@ -10,7 +10,6 @@
   - [Requirements](#requirements)
   - [Supported compilers](#supported-compilers)
   - [Build with CMake](#build-with-cmake)
-  - [Build with make](#build-with-make)
   - [Build with fortran-lang/fpm](#build-with-fortran-langfpm)
 * [Using stdlib in your project](#using-stdlib-in-your-project)
 * [Documentation](#documentation)
@@ -168,32 +167,6 @@ If at some point you wish to recompile `stdlib` with different options, you migh
 want to delete the `build` folder. This will ensure that cached variables from
 earlier builds do not affect the new build.
 
-
-### Build with make
-
-Alternatively, you can build using provided Makefiles:
-
-```sh
-make -f Makefile.manual
-```
-
-You can limit the maximum rank by setting ``-DMAXRANK=<num>`` in the ``ADD_FYPPFLAGS`` environment variable (which can reduce the compilation time):
-
-```sh
-make -f Makefile.manual ADD_FYPPFLAGS=-DMAXRANK=4
-```
-
-You can also specify the compiler and compiler-flags by setting the ``FC`` and ``FFLAGS`` environmental variables. Among other things, this facilitates use of compiler optimizations that are not specified in the Makefile.manual defaults.
-```sh
-make -f Makefile.manual ADD_FYPPFLAGS=-DMAXRANK=4 FC=gfortran FFLAGS="-O3"
-```
-
-On some systems, ``make`` selects the wrong default compiler. If you encounter error messages like ``make[1]: f77: No such file or directory`` set ``FC`` to your preferred compiler (e.g., ``gfortran``) or try
-
-```sh
-make -f Makefile.manual --no-builtin-variables
-```
-
 ### Build with [fortran-lang/fpm](https://github.com/fortran-lang/fpm)
 
 Fortran Package Manager (fpm) is a package manager and build system for Fortran.   

WORKFLOW.md

@@ -113,20 +113,3 @@ The project is usable as CMake subproject. Explicit references to
 break subproject builds.
 An example project is available [here](https://github.com/fortran-lang/stdlib-cmake-example)
 to test the CMake subproject integration.
-
-
-### Make build files
-
-The build files for ``make`` are using the name ``Makefile.manual`` to
-not conflict with the in-tree build of CMake.
-This project uses recursive make to transverse the subdirectory structure
-from the top-level makefile, called ``Makefile.manual``, and the build
-happens in-tree, *i.e.* build artifacts are present along with the source code.
-
-New source files are added in ``src/Makefile.manual`` and include manual
-dependency definitions through the object files to allow parallel
-compilation.
-Tests are generated by the make include file ``src/tests/Makefile.manual.test.mk``
-and defined in the subdirectories of the ``src/tests`` as entries in ``PROGS_SRC``.
-New subdirectories have to be explicitly added to ``src/tests/Makefile.manual``
-or are ignored.