Add onnx

[justinchuby]

No description provided.

[justinchuby]

@agriyakhetarpal I get

/home/runner/miniconda3/envs/pyodide-env/share/cmake-3.31/Modules/FindPackageHan
dleStandardArgs.cmake:233 (message):                                            
  Could NOT find Python3 (missing: Python3_INCLUDE_DIRS Development.Module      
  Development.SABIModule)                                                       
Call Stack (most recent call first):                                            
  /home/runner/miniconda3/envs/pyodide-env/share/cmake-3.31/Modules/FindPackageH
andleStandardArgs.cmake:603 (_FPHSA_FAILURE_MESSAGE)                            
  /home/runner/miniconda3/envs/pyodide-env/share/cmake-3.31/Modules/FindPython/S
upport.cmake:4000 (find_package_handle_standard_args)                           
  /home/runner/miniconda3/envs/pyodide-env/share/cmake-3.31/Modules/FindPython3.
cmake:602 (include)                                                             
  CMakeLists.txt:141 (find_package)           

Could you suggest the correct way to find python in pyodide?

[agriyakhetarpal]

Hi @justinchuby, I had a quick glance over the packaging structure for onnx, and I don't think it uses CMake's FindPython mode, but rather the previous method of getting the Python executable: https://github.com/onnx/onnx/blob/9c31fa6d39400d444c6b1a4de2a247ad32174f63/setup.py#L185. The FindPython mode is used by many CMake-based packages and it works for their builds. I would suggest trying with replacing Python3_EXECUTABLE to Python_EXECUTABLE once, but I doubt that would work. Next I would suggest trying to just use sys.executable instead of trying to find Python by working through sysconfig and getting the components based on the locations from the include directory. I see that Windows already uses sys.executable.

[agriyakhetarpal]

Looks like there are some discussions about this function already that you are a participant of: onnx/onnx#7226