On 31/10/19 5:21 pm, Sebastian Huber wrote: > On 30/10/2019 21:39, Chris Johns wrote: >> On 31/10/19 12:24 am, Sebastian Huber wrote: >>> On 25/10/2019 01:18, Chris Johns wrote: >>>> On 24/10/19 9:52 pm, Andrew Butterfield wrote: >>>>> I got around to doing a doorstop install that does not rely on >>>>> homebrew, >>>>> using the python.org <http://python.org> distribution for 3.8 >>>>> >>>>> Everything worked fine - python3 is installed in /Library just like the >>>>> OS X >>>>> native python 2.7 >>>>> Doorstop runs just fine too. >>>> >>>> Excellent and thanks for this. I think this or the other solution that was >>>> posted should work. This means I cannot see any blockers for Doorstop on >>>> our >>>> supported hosts. >>> >>> Ok, great. Thanks for all the testing and other valuable input. >>> >>> I think on macOS we have now five options: >>> >>> 1. homebrew >>> >>> 2. MacPorts >>> >>> 3. python.org installer >>> >>> 4. pyenv >>> >>> 5. wait for Apple to ship a Python 3 >>> >>> We need a recommendation for the user manual. >>> >> >> I suggest 3. because it is the simplest to do and it does not step on global >> paths. > > Ok. > >> >> Can we assume Doorstop is only needed if developing or maintaining RTEMS? > > Yes, definitely. > > You mean the user manual is not the right place to add Python 3.6+ to the host > computer requirements? We could add this to the RTEMS Software Engineering > manual. >
Good question. If there is nothing in the User Manual related to developing or maintaining RTEMS then yes the eng manual would be the correct place. I am sure we will find other things that are specific to each host. For example I will need to add a section to the eng manual on the release procedure and this has a range of specific packages that are needed. Chris _______________________________________________ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users