smalers
commented
5 years ago Useful content but not relevant to current environment since development environment has been cleaned up:
-
[JHB] Rather than deal with DOS shell environment issues, I found myself always using the special mingw shell where everything (git, make, gfortran, etc.) just works like it does in linux bash shells. The problem is that it puts your "home" in a deep dark path somewhere hard to find. And path separators are the linux style. Which brings up another issue...there are some Windows only and Linux only coding situations...which can be handled with custom make files, or code that you have to adjust internally or compiler level instructions. None of these are happy solutions to me. In statemod, I have linux only and windows only .for files, and let the make file handle it. In other words, in windows, USE THE WINDOWS SPECIFIC MAKE FILE!
-
[JHB] And I generally used the command line compile method, rather than the built in Eclipse features. Since I have only been compiling StateMod in recent years, this is the example I am talking mostly about in my comments here.
-
[JHB] Wow, lots of work to do below. A decade or more ago there were several flow charts and diagrams of StateCU code logic and organization. At some point it will be worth a question to LRE to see if my paper files and computer files are still available. Maybe Erin kept all this stuff, she also spent a lot of time coding StateCU back then. I made diagrams and used them when coding. Also, on the GUI side, updates to the GUI - Wizard and Excel graphing features and etc - (PM was Erin and Kara) was also carefully documented and prototyped and demonstrated to the State. Some of that info hopefully is still around and could be useful.
Jim Brannon responded to the documentation review request by doing a pull request. Significant edits have occurred to the documentation. Therefore, review the comments and make edits to documentation if still needed. Then will close the pull request.