Forwarding Gavin's comments with his agreement. On 2021-08-07 10:56, Stefan Fröhling wrote:
> if there is no manager assigned for the GCC development I would like > to take the part of the project manager for GCC. The aim is to > coordinate, structure and speed up the GCC development. Good for you. > The aim is to have a GCC developer team. Good luck with recruitment. I do not offer myself because I am 82; you need younger, better-skilled, more serious people. > I think that GCC is one of the most important applications for RISC OS > as it is the main tool to port open source application to RISC OS. It > is also the only C++ compiler for RISC OS. So GCC is one of the most > important tools for RISC OS and should not be neglected by the RISC OS > community. I agree. Without the patient help of Lee Noar I would never have been able to use !GCC at all. Of course !GCC seems bloated to RISC OS users, both in its documentation and in the binaries that it produces. The problem with the documentation could easily be solved by having someone suitably qualified strip out the parts that apply only to other platforms, to create a leaner documentation for RISC OS users only. If others are like me, then many potential users are put off by lack of experience with the syntax of make files. More examples and tutorial material would be useful. The Unix world is, perhaps necessarily, full of what I might call "jumbo-jet pilots": people who are not fazed by complexity. Whereas RISC OS users are more used to (over)simplicity. I think this psychological difference is an important factor in the success of your project. Good luck!
_______________________________________________ GCCSDK mailing list gcc@gccsdk.riscos.info Bugzilla: http://www.riscos.info/bugzilla/index.cgi List Info: http://www.riscos.info/mailman/listinfo/gcc Main Page: http://www.riscos.info/index.php/GCCSDK
