CI Failure

[pradal]

Related to issue #69

[AurelienBesnier]

Ubuntu is fixed. However for mac there seems to be a c++ library problem:
/Applications/Xcode_15.2.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/v1/cstdlib:144:9: error: no member named 'at_quick_exit' in the global namespace
Seems to be related to the Mac SDK

[AurelienBesnier]

For Windows, the setup of visual studio seems to be failing for some reason

[baugetfa]

I don't know if it could help, but on a fresh virtual windows-8.1, with python 3.9 (above it does not pass compatibility for the env), I got the same exit error than the CI at the same moment plantgl_conda_build_log.txt, with the following error:
`
le point d'entree de procedure SetThreadDescription est introuvable dans la bibliothèque de liens dynamiques

C:\Users\FB\miniconda3\envs\plg\conda-bld\openalea.plantgl_1744982685671_build_env\Library\bin\uv.dll
`

[pradal]

Thanks

Ubuntu is fixed. However for mac there seems to be a c++ library problem: /Applications/Xcode_15.2.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/v1/cstdlib:144:9: error: no member named 'at_quick_exit' in the global namespace Seems to be related to the Mac SDK

This can be due to a wrong definition of
MACOSX_DEPLOYMENT_TARGET (mismatch between libc++ and system)

[pradal]

@AurelienBesnier : Great thank you!

[AurelienBesnier]

@pradal no problem!
But it still doesn't work after changing sdk version

[AurelienBesnier]

The current setup of the meta.yaml + conda_build_config.yaml works on @christian34 's computer.
We are trying to fix the setup of the windows runner

[pradal]

@AurelienBesnier : it seems that the version of the compilers is managed in the file conda-build-config.yaml

In the https://github.com/conda-forge/conda-forge-pinning-feedstock you have the two lines:

  - vs2019                     # [win and x86_64]
  - vs2022                     # [win and arm64]

Not sure it helps, but this is a good guideline to be in sync with onda-forge

[AurelienBesnier]

Ok so, it seems to start working when we get rid of the previous action that sets up the install of VS and only mention the version of VS in the conda_build_config.yaml.

Problem is, we start to have some compilation errors.

[pradal]

@AurelienBesnier Great progress! Thanks.
If there are errors, it mmay be mainly due to the environment setting.
A long way, but we can act on it now.

[pradal]

@christian34 It works guy! So smart...

[christian34]

Bingo !!!

The two lines :
` - vs2019 # [win and x86_64]

• vs2022 # [win and arm64]`

mentioned above in the conf seems then to be the better solution !

Concerning the action I will submit PR for removing the msvc action. Probably some lines/howto use msvc will be needed in the guidelines !