-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Commented out debug statement causing compilation failure on OSX. #35
Conversation
@@ -102,8 +102,8 @@ | |||
connect(m_pMasterLatency, SIGNAL(valueChanged(double)), | |||
this, SLOT(masterLatencyChanged(double))); | |||
|
|||
qDebug() << "RLimit Cur " << RLimit::getCurRtPrio(); |
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.
maybe wrap these in a linux-specific ifdef instead?
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.
That makes sense. I can enclose them in the ifdef that follows, which weirdly doesn't encapsulate the body of the if statement. I compared it to older code and the if body code is new and should be included in the ifdef as far as I can tell.
Maybe we can drop these debug messages entirely later. But for now it is a good solution. Thank you Carl! |
fix compilation failure on OSX.
revamp Hardware Setup chapter
Two debugging lines introduced in dlgprefsound.cpp in commit aa2f6bf caused compilation failure on Mac OSX because they referenced Linux specific rlimit code. Removing them fixes the compilation failure.