[question] windres: Command not found #17304
Assignees
Labels
Comments
|
Thanks for your question. Some quick hints first:
There might be some limitations in some recipes that might not be prepared for all cases of cross-compiling. If not, please try to provide the full command line that you are using to reproduce, something like your: And also provide the full output. Please also confirm if you are using all recipes from ConanCenter, just in case. Thanks for your feedback! |
|
Thanks for your answers! I have also tried not using conan version: The complete command and output are as follows: |
|
I also tried to use |
|
Thanks very much for the feedback. In some cases, it can help to define the But from a quick look, it doesn't seem that this would fix it (give it a try, just in case, if you can). |
|
Thanks for your idea. It seems that the |
|
I looked through the source code of zlib and found that he had such a compiled code. libiconv is compiled with pure makefiles, and there is no similar operation. |
|
Same thing happens if you try to build libiconv/1.17 using the conan provided mingw-64 package which indeed also sets the It looks to me that problem lies mainly in the fact that the libiconv conan recipe really wants to bypass the
For this reason the variable gets ignored :( As a quick hack I changed the line to:
And sure enough it cross-compiles fine by correctly picking up the |
|
Hi @Slashcash I am not sure what could be happening in your case. Do you mean using the And then: It builds libiconv with mingw without problems, it doesn't require any modification to the recipe. |
|
Sorry, I realized I explained it pretty badly :D I was talking about cross-compiling libiconv from Linux to Windows using the conan provided mingw-w64 toolchain. The attempt to cross-compile using that toolchain fails in the very same way reported by OP
I was just reporting the fact that it happens both with a self-provided toolchain and the one coming from the conan package. You can actually replicate this by doing: target profile: build profile: and then:
As I was saying in the previous post I suspect it happens because of this configure args in the libiconv recipe: It looks to me they are forcing the RC and WINDRES to arbitrary values and the package_tool provided values of the same variables are ignored for this reason (causing the error to show up) For this reason if you switch that line to: I suspect that something on the line of (pseudocode): Would fix this issue without causing any disruptive damage to the recipe, but I am not knowledgeable enough to know for sure |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is your question?
An error occurs when cross-platform compiling a Windows package on a Linux system.
The package is
libiconv/1.17I have modified the profile file according to another issue, but an error has been reported. #14635
But I compiled the package
zlib/1.3.1of this issue successfully.My host profile:
My build profile:
And my x86_64-w64-mingw32-windres program exists.
I have searched the internet for a long time but couldn't find a solution. Thank you very much for your help.
Have you read the CONTRIBUTING guide?
The text was updated successfully, but these errors were encountered: