Changes between Version 19 and Version 20 of DevNotes/DevGuide/CondaDevSetup

Timestamp:

Jan 18, 2018 12:23:17 PM (6 years ago)

Author:

richardh

Comment:

richard added some extra notes

DevNotes/DevGuide/CondaDevSetup

@@ -3 +3 @@
 Download the latest '''64-Bit''' Python '''2.7''' Installer from http://continuum.io/downloads and run it.
 
- * The recommended destination folder is as good as any.  If you deviate from this then it's probably worthwhile to make sure the path is short and contains no spaces.
+ * The recommended destination folder is as good as any.  If you deviate from this then it's probably worthwhile to make sure the path is short and contains no spaces, and is not the same as any previous installation (one reader installed 64 bit on top of previous 32 bit, not a good idea).
 
  * At the Advanced Options screen, you need to consider whether or not you want to make Anaconda your default version of Python.  Developers who do not work on multiple Python projects can just accept the defaults here.
 
- * By default of Windows anaconda is installed for single user and not "everyone", which means you cannot run the conda command from an arbitrary command window. If you proceeded with default installation, you need to open Anaconda Prompt from Menu Start. Otherwise you can install anaconda for everyone, which requires root privlidges. 
+ * By default of Windows anaconda is installed for single user and not "everyone", which means you cannot run the conda command from an arbitrary command window. If you proceeded with default installation, you need to open Anaconda Prompt from Menu Start. Otherwise you can install anaconda for everyone, which requires root privlidges. If "conda" is not a recognised command then add the install directory to your Windows user Path variable.
 
 == Step 2 - Download !SasView and sasmodels from github ==
@@ -16 +16 @@
 git clone https://github.com/SasView/sasmodels.git sasmodels
 }}}
-
-
 == Step 3 - Install dependencies using yml files ==
 Go to folder:
@@ -41 +39 @@
 activate sasview
 
+else if running from inside a Git Bash shell then use: source activate sasview.
+
 #Mac OSX and Linux
 source activate sasview
 }}}
-
 == Step 5 - run !SasView ==
-You should be ready to run sasview. 
-Go to sasview directory and run
+You should be ready to run sasview.  Go to sasview directory and run
 
 {{{
@@ -57 +55 @@
 pythonw run.py
 
+To build the documentation you will still first need to do:
+
+python setup.py docs 
+
 }}}
-== [=#anchor1 Step 6 - Install Git (Optional)] ==
+== [=#anchor1 Step 6 - try the new qt gui (highly experimental work in progress)] ==
+''Some notes as of 18 Jan 2018 based on a Windows 7 install. Start with Git bash in your sasview directory.''
+
+source deactivate
+
+git checkout ESS_GUI
+
+''Look for sasview/build_tools/conda_py3_qt5.yml, open it in an editor, save it somewhere else outside of git control, '''remove''' any pip lines for sasview and sasmodels which will elsewise throw errors. (Also added a line  ''  - tinycc==1.1  '' but don't know if that was absolutely necessary)''
+
+conda env create -f=/path to your new yml file/conda_py3_qt5_new.yml
+
+source activate qt5
+
+cd src/sas/qtgui
+
+python convertUI.py
+
+cd ../../..
+
+python run.py
+
+''You may then need to install 64 bit Microsoft Visual C++ 14.0 compiler by following the link requested, as the latest changes to use only TinyCC compiler are not yet merged with this branch. Other useful conda commands:''
+
+conda info --envs      ''will show that you now have both sasview and qt5 environments.''
+
+conda env remove --name qt5''  ''
+
+''will remove the qt5 environment, though the files involved seem to stay on your hard drive so a new ''conda env create ''is much faster than the first time.''
+
+''If it does not work the first time through, try going back to the normal sasview master, then repeat the steps above. Piotr and others will be making this easier in the future.''
+
+== [=#anchor1 Step 7 - Install Git (Optional)] ==
 Install Git for your platform by following instructions:
 
@@ -72 +105 @@
 git config --global user.email johndoe@example.com
 }}}
+If you work behind proxy remmber to configure
 
-If you work behind proxy remmber to configure
 {{{
 e.g. git config --global http.proxy 192.168.1.1:XXXX