When running on mac without X-code command line tools, guide user to check whether the GPU works before having them install X-code.
After noting that the compiler isn't available and OpenCL isn't selected, open up the OpenCL options dialog so the user can immediately address the problem. Disable the "No OpenCL" option, but add a help button that instructs users to install the tools. Or optionally, leave the button available but pop up a dialog telling them to install command line tools when the option is selected.
Alternatively, automatically run the OpenCL tests when no command line tool is available. Need a dialog indicating test progress.
{
"status": "new",
"changetime": "2018-11-02T17:42:59",
"_ts": "2018-11-02 17:42:59.583377+00:00",
"description": "Sasview 4.2, Mac.\n\nWhen running on mac without X-code command line tools, guide user to check whether the GPU works before having them install X-code.\n\nAfter noting that the compiler isn't available and OpenCL isn't selected, open up the OpenCL options dialog so the user can immediately address the problem. Disable the \"No OpenCL\" option, but add a help button that instructs users to install the tools. Or optionally, leave the button available but pop up a dialog telling them to install command line tools when the option is selected.\n\nAlternatively, automatically run the OpenCL tests when no command line tool is available. Need a dialog indicating test progress.\n",
"reporter": "pkienzle",
"cc": "",
"resolution": "",
"workpackage": "SasView Bug Fixing",
"time": "2018-11-02T17:42:59",
"component": "SasView",
"summary": "redo mac startup notification",
"priority": "major",
"keywords": "",
"milestone": "SasView 4.3.0",
"owner": "",
"type": "defect"
}
I don't think this rises to the level that we should work hard to find resources for 4.x. However expect this also applies to 5.x so moving it to 5.1 - Otherwise it moves to the graveyard
Sasview 4.2, Mac.
When running on mac without X-code command line tools, guide user to check whether the GPU works before having them install X-code.
After noting that the compiler isn't available and OpenCL isn't selected, open up the OpenCL options dialog so the user can immediately address the problem. Disable the "No OpenCL" option, but add a help button that instructs users to install the tools. Or optionally, leave the button available but pop up a dialog telling them to install command line tools when the option is selected.
Alternatively, automatically run the OpenCL tests when no command line tool is available. Need a dialog indicating test progress.
Migrated from http://trac.sasview.org/ticket/1208