@duncanmmacleod - you need to run
VsDevCmd.bat -arch=amd64to set up the correct environment variables for conda build to see the msvc compiler
thanks @dhirschfeld, I tried this and got some new path entries, but still no cl.exe, if I run
VsDevCmd.bat -test that fails because it too cannot find
cl.exe. I presume I've done something wrong in installing VS in the first place, will investigate
C:\Miniconda\conda-bldand Appveyor goes for
C:\bld... I can reproduce the Appveyor behavior in my windows box, which also uses
C:\bld. Is that the reason? The PR is here conda-forge/staged-recipes#9163
[win and vc<14]
Can someone on core pull conda versions 4.7.11 and 4.7.12? Both of those versions break staged-recipes.
can someone help me with an appveyor failure on conda-forge/lscsoft-glue-feedstock#12, I am seeing
ModuleNotFoundError: No module named 'libarchive'
from all of the appveyor builds (we still need those, right?), thanks
conda install packageit will pop out a list of all the packages it will pull to install in my current env/arch - is there a way to test what it would pull for the same package on a different arch? Just trying to avoid having to set up a bunch of VMs to see how a package installs on different architectures
get-docker-secretyesterday and it was merge. Looking today at its feedstock, there are no build for it. I have created the following issue: conda-forge/get-docker-secret-feedstock#1