08-13-2020, 02:15 PM
Some responses:
- I agree that Code:Blocks is not an ideal solution in various ways. It has a GUI, which can be nice, but it also has some quirks. The major objective was to get away from the Lahey compiler that Bill was using and the Code::Blocks approach is at least one option. We had tried some other approaches, but we were not able to finish them. Also, if files are added/removed from the source code, you just have to adjust them in C::B. That is a quick change (most of the time consuming aspect is the setup and internal options which remain).
- On that note, a few people tried to use Makefiles, but were not successful (hence C::B is the default approach today). But if you able to come up with a Makefile, then that is exactly what we need, so thanks!
- Regaring Cean's attempt (https://www.mystran.com/forums/showthread.php?tid=38), there was a time when we removed BANDIT was removed from the code (since it needed to be touched up). Later, Bill reworked it we added it back into the source code. So it may be that it was not part of the code at all when Cean worked on it.
- In any case, we can use all the help/options we can get. So if you are successful, we can add the processes and/or adjust the source code as necessary. Ideally, we would like a non C::B option for Windows as well, but something for Linux would be great. We haven't had any developers interested on the Linux side yet, but it seems are few more are interested now. Also, we are lacking a Linux 11.0 build, so it would be good to add that for end users.
- I agree that Code:Blocks is not an ideal solution in various ways. It has a GUI, which can be nice, but it also has some quirks. The major objective was to get away from the Lahey compiler that Bill was using and the Code::Blocks approach is at least one option. We had tried some other approaches, but we were not able to finish them. Also, if files are added/removed from the source code, you just have to adjust them in C::B. That is a quick change (most of the time consuming aspect is the setup and internal options which remain).
- On that note, a few people tried to use Makefiles, but were not successful (hence C::B is the default approach today). But if you able to come up with a Makefile, then that is exactly what we need, so thanks!
- Regaring Cean's attempt (https://www.mystran.com/forums/showthread.php?tid=38), there was a time when we removed BANDIT was removed from the code (since it needed to be touched up). Later, Bill reworked it we added it back into the source code. So it may be that it was not part of the code at all when Cean worked on it.
- In any case, we can use all the help/options we can get. So if you are successful, we can add the processes and/or adjust the source code as necessary. Ideally, we would like a non C::B option for Windows as well, but something for Linux would be great. We haven't had any developers interested on the Linux side yet, but it seems are few more are interested now. Also, we are lacking a Linux 11.0 build, so it would be good to add that for end users.