Black control groups when rebuilding on OSX Mojave #2555
Comments
|
Could you post your |
|
@vojtechkral you are right that I was not targeting the correct OS version. I managed to set this to 10.9 as the instructions state, but then I run into this error when I run
Which seems to be the same issue here that you commented on pnggroup/libpng#187. What do I need to change to get past this? |
|
@Quintox303 I have the same advice for you as for OP - please post Edit: If you're unsure how to collect and also please remove the file (Sorry if you already know all of this - sometimes I have a hard time remembering who is/isn't a programmer in issues discussions...) |
|
@vojtechkral I was reporting on behalf of @Quintox303 for this issue. |
|
@vojtechkral Here are my cmake outputs. Hopefully this can help diagnose the issue. I managed to get past that error that my last comment was about, but the black control groups are still present. Here are the outputs: Cmake of dependencies Cmake of PrusaSlicer |
|
@Quintox303 I took the liberty and edited your comment, fixing formatting for clarity. (No content changed.) In any case, here's the problem: The deployment target doesn't match the SDK used. I'm not sure how this happened, but you probably want to build for newer Mac OS 10.14. To do this, set Alternatively if you wanted to build for 10.9, you'd need to download the appropriate SDK. Hope this helps. |
|
I'm observing the same issue. Here's the output of cmake for deps: Here's the output of cmake for prusaslicer itself: I'm on MacOS 10.14.5. |
|
I rebuilt again with the deployment target corrected and I have the same results. I am also on MacOS 10.14.5. Here are my cmake outputs deps: prusaslicer: |
|
Ok, thanks, I'll have a look... |
|
I have the same issue. My workaround is to set up the print in the regular release, then save the project and open it in my custom build to generate the actual print file. A fix would be highly appreciated! |
|
Allright, so I managed to reproduce the issue. It seems to happen both with wxWidgets 3.1.1-patched and 3.1.2-vanilla. At the moment I have no idea what causes this. It doesn't seem to be related to dark mode. Chances are this is a problem in wxWidgets, but I can say at the moment. If you need to build Slicer, as a workaround, you can build against SDK 10.9 like we do (but of course we recognize this isn't a real solution). |
|
This seems fixed now, I no longer have black areas when building in 10.14.6 against the default 10.14 SDK (building against 10.9 is broken by the way, some error about exceptions only being supported from 10.12 on). |
|
Should be fixed. Closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
Rebuilt from master @ b8f9d2e
Operating system type + version
OSX Mojave 10.14.5
Behavior
I attempted a rebuild from scratch on OSX following the instructions (https://github.com/prusa3d/PrusaSlicer/blob/master/doc/How%20to%20build%20-%20Mac%20OS.md)
"deps" built fine after two tweaks:
After that PrusaSlicer itself built fine and without problems.
But when running, the various setting tabs seen to have a black background in the option groups.
The first group in a tab is always fine, with the groups following always having a black background:
Any idea why this is the case?
Everything seems functional. If you change a setting the labels become orange, so the text is there but just invisible due to the background.
The system is running in the default "light"mode.
Ping @Quintox303
The text was updated successfully, but these errors were encountered: