[Fixed] conda build 0.19.20188 with linker errors

[UR_]

Since updating to this revision

2020-03-20 15:16:04 (rev 21)
libtiff {4.1.0 (conda-forge/win-64) -> 4.1.0 (conda-forge/win-64)}
vtk {8.2.0 (conda-forge/win-64) -> 8.2.0 (conda-forge/win-64)}


(freecad) C:\Users\aio\Miniconda3>conda list vtk
# packages in environment at C:\Users\aio\Miniconda3\envs\freecad:
#
# Name Version Build Channel
vtk 8.2.0 py38hb4a5736_210 conda-forge

(freecad) C:\Users\aio\Miniconda3>conda list libtiff
# packages in environment at C:\Users\aio\Miniconda3\envs\freecad:
#
# Name Version Build Channel
libtiff 4.1.0 h885aae3_6 conda-forge

I get these nasty paths:

3>------ Build started: Project: Fem, Configuration: Release x64 ------
3>LINK : fatal error LNK1181: cannot open input file 'D:\bld\vtk_1584655998548\_h_env\Library\lib\liblz4.lib'
3>Done building project "Fem.vcxproj" -- FAILED.

4>------ Build started: Project: FemGui, Configuration: Release x64 ----
4>LINK : fatal error LNK1181: cannot open input file 'D:\bld\vtk_1584655998548\_h_env\Library\lib\liblz4.lib'
4>Done building project "FemGui.vcxproj" -- FAILED.

Looks like some hardcoded paths are left.
How to get rid of them?

[looo]

reproduced: https://dev.azure.com/sppedflyer/feedst ... 9d50bbeacd
issue: https://github.com/conda-forge/vtk-feedstock/issues/106

Looking at the raw package it seems like a lot of such paths are not correctly replaced. So I guess this is a conda-build problem.
build 210: conda-build 3.19.1
build 209: conda-build 3.19.0

https://github.com/conda/conda-build/issues/3909

edit: best to pin older version of vtk until a new vtk-package with a fixed conda-build is available. The last freecad-build available from freecad/label/dev used vtk_8.2.0-py38h4a1a8eb_208

Code: Select all

conda install vtk=*=*_208

[looo]

updating vtk to latest version should be fine again. The path-replacement somehow was not working but is now working thanks to @seanyen:
https://github.com/conda-forge/ripgrep- ... ck/pull/12