-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rebuild for libtiff45 #40
Rebuild for libtiff45 #40
Conversation
…nda-forge-pinning 2023.03.09.00.59.00
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
@conda-forge-admin please rerender |
Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do. This message was generated by GitHub actions workflow run https://github.com/conda-forge/leptonica-feedstock/actions/runs/4620653519. |
@conda-forge-admin please restart ci |
@conda-forge-admin please restart cis |
…nda-forge-pinning 2023.07.02.05.17.29
Windows failure not obviously related to the libtiff update, but who knows?
|
Aha, appears to be related to |
…nda-forge-pinning 2023.07.10.11.48.20
OK, the latest version of |
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe:
|
I've gotten this farther, but now we're failing on (linewrapping added):
|
It seems to be trying to download and rebuild all the dependencies on windows. |
@hmaarrfk Oh, is that not the intention? I'm not familiar with this build ... |
It just seems very anti conda forge. Maybe it would be better to tackle each library independently. That said, this is something that the original maintainers may have to do. |
…nda-forge-pinning 2023.07.26.21.58.02
Revisiting this. I've tried merging in the update to 1.83.1, in case it happens to help with the most recent issue. edit: also, FWIW, it looks like previous successful builds of this package are downloading and building all of the dependencies, so that's not new. I don't love it either, but with these complex Windows packages, I'd rather not open that can of worms ... |
Maybe using jpeg turbo will help... |
So, the problem here seems to be that we have ended up with multiple versions of the command-line compilers installed on the machine:
The one that shows up in I think it will help to get everyone on the same page about which compiler we're using, but apparently you can't just tell CMake which compiler to use on Windows without jumping through some hoops, and it's not clear to me to tell |
As logged in `bld.bat`: as of July 2023, the build system for this package can run into issues if the version of `cl` found via %PATH% is not exactly the same as the version used by MSBuild. The only way I can figure out to avoid the problem is to avoid MSBuild altogether, which can be done by using the NMake Makefiles generator, as well as explicitly specifying the full path to the desired compilers. The error messages were: ``` Exception in file D:/dev/cppan2/client2/src/sw/driver/module.cpp:120, function operator (): error in module (C:/Users/VssAdministrator/.sw/storage/tmp/cfg/793929/loc.sw.self.4a156b-0.0.31.dll): Exception in file D:/dev/cppan2/client2/src/sw/driver/target/native.cpp:799, function findCompiler: Cannot find compiler com.Microsoft.VisualStudio.VC.cl->=19.35.0 <19.36.0 for settings: {...} ```
fe03b36
to
6a751b5
Compare
Woohoo, I think I figured out how to get this working. My solution does change the CMake build system from MSBuild to NMake, but I don't believe that should affect the resulting artifacts in any significant way. |
amazing! |
This PR has been triggered in an effort to update libtiff45.
Notes and instructions for merging this PR:
Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.
If this PR was opened in error or needs to be updated please add the
bot-rerun
label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase@conda-forge-admin, please rerun bot
in a PR comment to have theconda-forge-admin
add it for you.This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/4371839096, please use this URL for debugging.