Merge pull request #111 from dibenede/main

Fixup build and docs after move to standalone repo

Author: dibenede

README.md

@@ -37,14 +37,19 @@ If you want, you can compile `protoc` from source instead.  To do this
 follow the instructions in [the top-level
 README](https://github.com/protocolbuffers/protobuf/blob/main/src/README.md).
 
-Once you have `protoc` compiled, you can run the tests provided along with our project to examine whether it can run successfully. In order to do this, you should download the Protocol Buffer source code from the release page with the link above. Then extract the source code and navigate to the folder named `js` containing a `package.json` file and a series of test files. In this folder, you can run the commands below to run the tests automatically.
+Once you have `protoc` compiled, you can run the tests provided along with our
+project to examine whether it can run successfully. In order to do this, you
+should download the Protocol Buffer source code from the release page with the
+link above. Then extract the source code and navigate to the folder named `js`
+containing a `package.json` file and a series of test files. In this folder, you
+can run the commands below to run the tests automatically.
 
     $ npm install
-    $ npm test
+    $ PROTOC_INC=/usr/include/google/protobuf npm test
 
-    # If your protoc is somewhere else than ../src/protoc, instead do this.
-    # But make sure your protoc is the same version as this (or compatible)!
-    $ PROTOC=/usr/local/bin/protoc npm test
+`PROTOC_INC` specifies the protobuf include path. By default, we use `protoc`
+located from `PATH`. Optionally, you can use the `PROTOC` enviroment variable to
+specify an alternative `protoc`.
 
 This will run two separate copies of the tests: one that uses
 Closure Compiler style imports and one that uses CommonJS imports.