Closed tinrabuzin closed 8 years ago
I think there is several things to do here.
I will do nr 1. For nr 2. I think it is important to think of what the installation script should do, to make it easier for the end user. There are for sure several steps that we've become accustomed to do manually, but should be automated. Here your suggestion is welcome!
Suggestion:
Files are here: https://www.dropbox.com/sh/8vn1v3pd28f637o/AAA-Syk97-Za7OM6u4MDCRBZa?dl=0
I created a few of the functions that go through the structure of the RaPId directory and check for the toolbox that is required by each of the files.
Currently, the Matlab function that checks the dependancies of the particular .m files cannot recognise that the toolbox is missing (it only returns the toolboxes that are used AND installed on the computer where it is executed).
That is why I created 'dependancy_list.mat' by running my script on my computer with everything installed. dependancy_list.mat is created by running check_dependancies.m.
What I propose now is that the end user should run check_installed.m which loads dependancy_list.mat, compares it with installed toolboxes and gives a warning if there is something missing. I also added this check in the setup_rapid.m.
Let me know what you think! @MaximeBaudette @janlav @lvanfretti