Opened 9 years ago
Closed 8 years ago
#48740 closed enhancement (fixed)
qemu: +cocoa and +curses don't actually conflict.
| Reported by: | irony42@… | Owned by: | raimue (Rainer Müller) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | qemu |
Description
The qemu portfile errantly sets up +cocoa and +curses as conflicting variants.
Dunno when it changed, but for a while now qemu has been happy to install with multiple frontends enabled, and merely deleting the conflicts cocoa & conflicts curses attributes from the portfile allows building of a correctly-functioning qemu +cocoa+curses.
(There are also commented out variants that this should apply to; the only real conflicts are gtk2–gtk3 and sdl–sdl2)
Change History (5)
comment:1 Changed 9 years ago by Ionic (Mihai Moldovan)
| Cc: | raimue@… removed |
|---|---|
| Owner: | changed from macports-tickets@… to raimue@… |
comment:2 Changed 9 years ago by raimue (Rainer Müller)
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:3 Changed 9 years ago by irony42@…
Weird. Running the curses frontend with -curses (rather than -display curses) does seem to work correctly, without opening any empty Cocoa windows.
comment:4 Changed 9 years ago by raimue (Rainer Müller)
| Resolution: | wontfix |
|---|---|
| Status: | closed → reopened |
You are correct. I wasn't aware of this peculiarity. I submitted a patch for upstream and will also apply it to the port once it reaches their master.
Furthermore I tested again with the current version and the remaining conflicts will be
- +gtk2 and +gtk3 (can only link against one of them)
- +sdl/+sdl2 and +cocoa (Cocoa is internally handled as display type
DT_SDL)
comment:5 Changed 8 years ago by raimue (Rainer Müller)
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Patch applied in r142228, +cocoa and +curses no longer conflict.
They do conflict. If you try to run the curses frontend (
-display curses) with +curses+cocoa, an empty Cocoa window will open. This is due to the fact that Cocoa support needs to be implemented a bit different. These conflicts do not exist on other platforms.