Compiling on Windows
Knowledge Base | conda-forge | community-driven packaging for conda
Win: Alternative to MKL · Issue #257 · conda-forge/scipy-feedstock · GitHub
■
Handling difference in long type in C between unix and windows
NumPy2 lighning talk: Change `np.int`_ to `np.int64` on all platforms - HackMD
np.int64 in python and int64_t in c instead of long would be the choice...
Additional information: API: Make 64bit default integer on 64bit windows by seberg · Pull Request #24224 · numpy/numpy · GitHub
Finally it was found that dtype="int_" and dtype="long" behave differently on Windows. The latter was necessary.
■
conda meta.yaml selectors
Defining metadata (meta.yaml) — conda-build 0.0.0.dev0+placeholder documentation
How to handle test data in conda-build
conda build - recommended way to add heavy test data - Stack Overflow
■
Using gh to access private repos via https (e.g. when ssh not allowed)
Settings -> Developer Settings -> Personal access token -> Fine-grained personal access tokens
Do not forget setting "Contents : Read-only" in "Permissions".
gh auth login --with-token < github-token
If wanted to set credential.helper
gh auth refresh
[remote "origin"]
url = https://github.com/foo/bar.git
git pull
GitHub Actions でプライベートリポジトリを checkout する (japanese)
■
nanobind & scikit-build-core & cmake
CMake API Reference - nanobind documentation
Configuration - scikit-build-core 0.9.9.dev7 documentation
tool.scikit-build.cmake.define
lapacke
How to link LAPACKE to a c++ project using cmake? - Stack Overflow
■
Making conda package: do we need build.sh?
This page was very helpful. https://stackoverflow.com/questions/76228791/conda-23-3-1-what-shall-be-the-content-of-build-sh
