Install for dev under windows

[baugetfa]

Just for memo.

Under windows I tried to follow the readme on branch dev_cyril that did not work (I think because I do not have Visual Studio C++ installed) I had to do some modifs as follows:

conda create -n pyratp_dev -c conda-forge -c openalea3 openalea.plantgl openalea.mtg qtpy m2w64-toolchain meson-python=0.17 scipy pytest jupyter python

conda activate pyratp_dev

set CC=gcc
set CXX=g++

pip install .

The modifications:

1. removed gfortran (comes with m2w64) and set meson-python=0.17
2. set environment variables, otherwise try to use cl.exe from visualstudio

[baugetfa]

Just for memo again.
The above solution had at least one drawback which is the environment variables have to be set at each new terminal. Here another solution more durable:

1. in root dir create a native.ini file with:

[binaries]
c = 'gcc'
cpp = 'g++'

2. And add to pyproject.toml:

[tool.meson-python.args]
setup = ['--native-file=native.ini']

Then follow the above command line without the set CC and set CXX.
A big drawback, that does not work on Linux and Mac.

[pradal]

Is this syntax working?

[tool.meson-python.args]
setup = ['--native-file=native.ini; ; os_name == "nt"']

[baugetfa]

No that only works for dependencies.
I think the solution would be to add script to manage that outside pyproject.toml. But does it the solution ? Not sure. I think the meson's files must be reviewed. Or it is only for windows developers, so they can locally have there pyproject.toml without pushing it.

[pradal]

This is a real limitation of meson. There is no way to have a native configuration file that is OS specific.
But we can raise an error on windows if it is not gcc.

[baugetfa]

I do not like the idea of raising an error, and it is raising an error if it is not gcc and g++ set because by default it is looking for cl.exe. I think that specifying to windows developers to modify locally their pyproject.toml is the easiest thing.