Changes between Initial Version and Version 1 of Ticket #1000, comment 6


Ignore:
Timestamp:
Jan 11, 2018 3:36:22 AM (7 years ago)
Author:
wojciech
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1000, comment 6

    initial v1  
    11I've managed to reproduce the behaviour on the fresh OSX 10.12 but I think SasView behaves as expected.  
    22 
    3 1. When you run sasview for the first time (on the fresh system) it asks for installing xcdoe command line tools. When you click on "Not Now" button it will skip installation but will raise a proper error when you try to compile with c compiler "No OpenCL" ticked 
     31. When you run sasview for the first time (on the fresh system) it asks for installing xcdoe command line tools. [[Image(Screen Shot 2018-01-11 at 09.03.16.png​)]] When you click on "Not Now" button it will skip installation but will raise a proper error when you try to compile with c compiler - "No OpenCl" ticked [[Image( Screen Shot 2018-01-11 at 09.04.07.png)]] 
    44 
    5 2. When you then untick "No Opencl" sasview will fall back to GPU compilations and then the models get compiled.  
     52. When you then untick "No Opencl" sasview will fall back to GPU compilations and then the models get compiled with OpenCl.  
    66 
    7 3. But still when you tick "No OpenCl" again and try to compile with c compiler again it raises proper error again and pops up Xcode installation dialog.  
     73. But still when you tick "No OpenCl" again and try to compile with c compiler again it raises proper error again and pops up Xcode installation dialog.[[Image(Screen Shot 2018-01-11 at 09.27.54.png)]]  
    88 
    99So it seems that Xcode is persitant enough to force c compiler installation.