Keep cmake_example and python_example in sync as much as possible about cmake_example HOT 3 CLOSED

The projects should be in sync now with the bulk of the changes in #5 and pybind/python_example#14.
I don't expect any huge changes in the future, so the sync should be easy to maintain.

from cmake_example.

I agree. On the cmake_example side, the main.cpp file should be updated to match the one from python_example. With the docstrings in place, the sphinx docs folder could also be added.

In the other direction, if you are open to it, I believe that the .travis.yml and .appveyor.yml files from cmake_example could be added to python_example. The installation procedures are identical so the CI configs would not require any changes. Although, those only test pip install, since I haven't gotten around to setting up Travis and AppVeyor for the conda recipe. But I'd like to include a test for that as well.

There is a little bit of divergence with regard to Windows: because CMake will internally pick the latest VS version and set the environment appropriately, there is no need to manually call vcvarsall.bat. I assume this would also be the case for the conda recipe in cmake_example, so those lines probably can be removed. But as I said, I have not yet gotten around to testing this.

from cmake_example.

I agree. On the cmake_example side, the main.cpp file should be updated to match the one from python_example. With the docstrings in place, the sphinx docs folder could also be added.

👍

In the other direction, if you are open to it, I believe that the .travis.yml and .appveyor.yml files from cmake_example could be added to python_example. [...]

Yes, that is a good idea.

There is a little bit of divergence with regard to Windows: because CMake will internally pick the latest VS version and set the environment appropriately, there is no need to manually specify vcvarsall.bat. [...]

Interesting.

from cmake_example.