Forum Replies Created
-
Posts
-
I have resolved this problem. I installed Brainsuite ver 19b, as well as the required MATLAB Runtime R2019b. Now svreg is working fine again.
I don’t have a clear idea of why it is now working, but I’m wondering if it could have something to do with having multiple MatLab Runtime versions installed, in addition to the full Matlab development environment (of yet a different version). I’m not aware of how the svreg code selects which Matlab environment to execute within — if it has to do with the order in which the different versions appear in the system PATH list, that could explain it. However, I tried messing with the order in the PATH variable and I couldn’t really reproduce the problem with ver 19b. So… who knows. I’m just happy it’s working again!
Thanks for your response. I will look for that new package next week.
I was using MSVC2017. I saw the ReadMe instructions to build using VS2013, but I figured bigger was better! So, obviously, no worries on that issue… I can get VS2013 if I really need to build the code.
By the way, many thanks for making this fantastic software available to the community.
Best regards,
TodJust a followup on my question. I downloaded the 17a source code (BrainSuite GUI v.17a and command line tool source code [ 5.5 MB ]), and tried building in Visual Studio.
I noticed that the build failed, due to errors in one “+” operator definition in file “BrainSuite17a_src\3rdParty\include\strideiterator.h”. After I fixed that one error, everything built correctly and I got the ten missing command line tools I had been missing.Could it be that, due to this one error, the command line tools failed to be included into the 17a release??
-Tod
I have just posted a similar question.
Have you had any resolution of your question?I’m wondering if we need to download the “BrainSuite GUI and command line tools [ 5.5 MB]” and build the command-line tools ourselves. Either that, or someone forgot to package the command line tools in the latest release!
-Tod
