-
Notifications
You must be signed in to change notification settings - Fork 19
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
Adding libxslt as a cross_input appears to not work. #11
Comments
|
I don't know what code you are using to find libexslt: your bug reports should include all the details necessary to reproduce the bug without us having to think too hard about it. Also, note that anything you get from |
Sorry. I am somewhat limited what I can share given I am working on proprietary code. I like that you managed to get qt cross compiling for windows. Huge props there. I might try to port your qt packages just as overlays within nixpkgs. That or trying to port my current overlays to nixcrpkgs. |
I'm glad you are enjoying the project! I do recommend using Qt 6 ( It looks like you're using QMake, so if you keep having trouble you could just make a minimal qmake file with 5-10 lines of code in it that produces the same error message, and post it along with the Nix file. Then I'd be able to reproduce the issue and might be able to help. |
So my knowledge of Qt is somewhat limited, but from what I can see in the MyprojectPro directory, I have a
|
Don't forget my previous comment:
Separately, I chose not to override the default behavior of https://github.com/pololu/nixcrpkgs/blob/cd1860e/wrappers/builder.sh Also, I don't think I did much work QMake and Qt 5. I used CMake for my applications, and I think I used only a small subset of the features provided by the Qt project's CMake files. So you might run into more problems along the way. |
Trying this a little differently... Here is how qmake is being invoked
Here is my flake
All of my attempts to add environment variables within the derivation appear to have no affect.
|
Maybe qmake is setting PKG_CONFIG_PATH somewhere and overriding what you're trying to do. Also, nixpkgs itself probably has setup scripts written in Bash which override it. You should at least print out the values of any environment variables you care about right before you run Sometimes in the past I actually have overridden P.S. I don't know much about flakes and I see you are still liberally mixing together native software and stuff that was cross-compiled with nixcrpkgs, which is likely to cause big problems. |
Oh yeah. |
I think what I originally had was better.
Oddly enough, this is the same error I get when trying to use qmake in nixpkgs. I guess what my question is more generally is how do you use a cross compiled package from nixpkgs when it does not exist in nixcrpkgs? |
You can add the package in your fork of nixcrpkgs the same way other packages are added. Or if you want the code to live outside of nixcrpkgs, when you evaluate nixcrpkgs, it returns a set and you can access the |
Oh, if you actually did succeed in cross-compiling a package with Nixpkgs and you want to use it with nixcrpkgs you could try putting it in the nixcrpkgs was designed to be its own set of packages that work well with each other and there hasn't been any attempt to make it interoperate with cross-compiled stuff from nixpkgs, so if you go that route you need to know that you are inventing something new and you will probably need to be a power user of the Nix language, the Nixpkgs code base, build systems, and compilers. The cross-compilation in Nixpkgs was pretty broken and/or lacking when I made nixcrpkgs and I'm not sure how much it has advanced. |
Here is my
nix/build.nix
The text was updated successfully, but these errors were encountered: