-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Qt: Do not require mkDerivation #108888
Qt: Do not require mkDerivation #108888
Conversation
@@ -39,6 +40,7 @@ stdenv.mkDerivation { | |||
|
|||
name = "qtbase-${version}"; | |||
inherit qtCompatVersion src version; | |||
inherit debug; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does this option do? In https://github.com/NixOS/nixpkgs/pull/109239/files#diff-a178028d8bf3d9cb5c68fe3e5856be45f904bc22e1b9c6f938ed3c7c386026fdR259 there was a configure flag require to have debug symbols.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know, that didn't used to be the case. This isn't a new option. The only thing "new" here, is that Qt will remember which option it was built with so that we don't have to pass a debug flag into every package that depends on it.
@@ -22,6 +22,7 @@ | |||
libGL, | |||
buildExamples ? false, | |||
buildTests ? false, | |||
debug ? false, | |||
developerBuild ? false, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the difference between debug and developerBuild?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to the upstream build documentation, a "developer build" is an in-source build of Qt for developers. I have no idea why that would be useful to have in Nixpkgs, but I will make sure that we respect that flag for the purpose of propagating the correct CFLAGS.
The qmake hook sets its own `CONFIG+=debug` or `CONFIG+=release` depending on how `qtbase` was built. We no longer rely on using the custom deriver for this feature.
6d1d780
to
c1c3205
Compare
The documentation is now up-to-date and I have integrated some recent changes to |
do you mind squashing related commits? Mostly looking at the ~6 fixup commits for qtbase-setup-hook.sh |
Tests pass, so I'll clean up the commit history and we'll be good to go. |
6779f25
to
13e3ec0
Compare
Motivation for this change
The return of #71089.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)