Windows Build system missmatch Console/Windows
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Fix Released
|
Low
|
RJ Skerry-Ryan |
Bug Description
The current build log contains both Console and Windows settings:
http://
```
Building with LINKFLAGS: /nologo /MACHINE:X86 /DEBUG /LTCG:NOSTATUS /OPT:REF /OPT:ICF /MANIFEST /nodefaultlib:
```
```
link /nologo /MACHINE:X86 /DEBUG /LTCG:NOSTATUS /OPT:REF /OPT:ICF /MANIFEST /nodefaultlib:
```
```
link /nologo /MACHINE:X86 /DEBUG /LTCG:NOSTATUS /OPT:REF /OPT:ICF /MANIFEST /nodefaultlib:
```
It looks like the current build is finally a Console Applikation, because it spans an undesired console window when double clicked.
The start link contains settings for the console which is typical for a console application.
After a double click start we are able to close the undesired console window, which will pop up.
We can go this way. It has the advantage that Mixxx behaves similar to the other Build targets.
The other solution is to be a Windows application and try to connect to a calling cmd.exe process. Do not know if this is possible.
But maybe we just don't need to do it, since we have the debug output in the developers menu.
I wonder how the "DEBUGCONSOLE" has worked in Mixxx 1.11. My first assumption that the console is fired up on demand only was wrong.
Changed in mixxx: | |
assignee: | nobody → RJ Ryan (rryan) |
status: | New → Confirmed |
Changed in mixxx: | |
milestone: | 2.0.0 → none |
importance: | Undecided → Low |
tags: | added: build |
Changed in mixxx: | |
milestone: | 2.2.0 → 2.3.0 |
status: | In Progress → Fix Committed |
Changed in mixxx: | |
status: | Fix Committed → Fix Released |
We may also make the debug build a console application and the release build a windows application ...