Removal of "No CMake" build option

[petervdonovan]

This branch deletes over 500 LOC and breaks the "no CMake" build option that directly invokes the C compiler. The corresponding PRs in reactor-c and reactor-c-py should be merged first.

It's a bit of a work-in-progress, but I wish to rush this into master to mitigate conflicts. I promise to help resolve any conflicts that result in the fed-gen branch.

[cmnrd]

In this case it should be helpful to get the verbose output of cmake and compare the executed commands in CI to a local run.

[petervdonovan]

I did as Christian suggested and can confirm that CMake is discovers a different version of Python than what is discovered by which python. To be specific, invocations of gcc include the option -isystem /usr/local/opt/python@3.10/Frameworks/Python.framework/Versions/3.10/include/python3.10 whereas when I SSH into the runner I see the following:

Mac-1666038353816:lingua-franca runner$ which python3
/usr/local/bin/python3
Mac-1666038353816:lingua-franca runner$ ls -al /usr/local/bin/python3
lrwxr-xr-x  1 runner  admin  40 Oct 11 00:31 /usr/local/bin/python3 -> ../Cellar/python@3.10/3.10.7/bin/python

Basically, one Python is in the Cellar, and the other is not.

There are ways to fix this, e.g., by explicitly specifying the path to Python when we invoke CMake.; furthermore, I know where in the code base this change would have to be made. However, there are a few reasons to stop here:

• Every build environment is different, and an end user can always find ways to break their build by setting up their environment in special ways. Arguably, whether this is a bug in the build system or in the environment is a matter of perspective.
• It is possible to work around this issue by using a virtual environment (which most Python programmers should do anyway).
• This bug has never been observed except in CI, and it could be very rare.
• It is not clear to me that other ways of integrating Python with CMake are recommended over the one I used; therefore, it is not obvious to me that fixing this bug would reduce the total number of bugs that we have.

[lhstrh]

This looks great! Congrats on finally getting this PR to pass the tests!! 🎆 I left some comments/requests. I wonder how much trouble these changes will give us in fed-gen... Perhaps you could assist with the merge? I haven't reviewed the changes in reactor-c yet. I will do that next.

[lhstrh]

Looks like there is no accompanying PR for reactor-c-py?