[core] Don't build cpp api on pip install

[dayshah]

Why are these changes needed?

Don't want to build the cpp api when using the pip install -e . --verbose command

Related issue number

Checks

• I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
• I've run scripts/format.sh to lint the changes in this PR.
• I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've added any new APIs to the API Reference. For example, if I added a
    method in Tune, I've added it in doc/source/tune/api/ under the
    corresponding .rst file.
• I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
• Testing Strategy
  • Unit tests
  • Release tests
  • This PR is not tested :(

[aslonnie]

I think this will break release wheel building? at least this is a behavior change.

[dayshah]

ray/python/setup.py

Lines 123 to 124 in 02d3f3c

	if os.getenv("RAY_INSTALL_CPP") == "1":
	# "ray-cpp" wheel package.

wouldn't cpp wheel building go down this path anyways and RAY_INSTALL_CPP has to be true

[aslonnie]

yeah.. you are right that when we are building for releases, we always set RAY_INSTALL_CPP=1 already.

[aslonnie]

yeah.. you are right that when we are building for releases, we always set RAY_INSTALL_CPP=1 already.

well, no, actually, RAY_INSTALL_CPP is used to toggle if to build the ray package or the ray-cpp package. it is not for controlling the cpp header files are built.