Buildserver: Optimize debug builds

[Daniel Schürmann]

Currently our builds are unoptimized.

optimize=off

We do not get comparable performance results with this setting.
The binaries are useless on older hardware.

We should use

optimize=portable

As we will do in the release.

[Daniel Schürmann (daschuer)]

Buy the way:
The flag was changed after:
http://downloads.mixxx.org/builds/master/mixxx-master-git5216-x86.exe

[Daniel Schürmann (daschuer)]

This bug is back see:
http://builds.mixxx.org:8081/jenkins/job/1.12-debug/36/architecture=amd64,platform=ubuntu/consoleFull

[RJ Skerry-Ryan (rryan)]

Oh shoot, I didn't notice the bug was about debug builds.

I think debug builds are for when we want a clean unoptimized stack trace, no?

[Daniel Schürmann (daschuer)]

Maybe I have just confused myself, because the use cases for the builds are unclear/undefined.
What is your definition for this? Who should install a debug build?

It is all because I never debug Mixxx unoptimized because the results are not comparable.
Where the debug builds really used for single stepping in the past?
Maybe we can just drop the debug builds from the build server, since most contributors will do single-stepping in their home made builds.

If we decide one day to disable qDebug for release we need a debug build again.
A debug build could be useful for the test suit, if we enable debug assertions as fatal.

[RJ Skerry-Ryan (rryan)]

We haven't produced debug builds for a while so this is kind of moot.

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/7936