It was only after 20 years of using Squeak that I was ever able to
successfully build my first VM ever, just the other day, and only because
the platform-specific instructions were good enough that even I was able to
figure out the missing libraries myself.

Whatever is being discussed here about the HowToBuild's, I hope it is not
about taking it back to some "generic" instructions that require expert C++
development knowledge to be able to figure out.  That's probably where the
idea that "no one reads it" came from because, sure, if it targets a
"members only" C++ experts audience that doesn't need documentation, it
won't get read.  Likewise, when non-experts (e.g., me) spend valuable time
trying, but failing, to build, it also won't get read again for a long
time, because it's safer to just keep scraping up pre-built binaries
wherever they can find them, rather than risk wasting more time failing to
build.

Being able to build makes Squeak more valuable.  Whatever the solution, I
hope this usability will not regress.

 - Chris

On Tue, Feb 2, 2021 at 12:22 PM tim Rowledge <tim at rowledge.org> wrote:

>
>
> > On 2021-02-02, at 1:07 AM, Tobias Pape <Das.Linux at gmx.de> wrote:
> >
> >
> > While it is true what you say, no-one is going to expect this dispersion
> or even read these infos.
> > You can say that this is not proper, and you might be right, but people
> just won't do it.
>
> So the solution is to link them together in some manner, surely? We do
> really need the different details for the various types of vm & platforms.
>
> Would it be plausible to use Markdown format to link sections, or build a
> bundled doc?
>
> tim
> --
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> Useful random insult:- Understands English as well as any parrot.
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20210202/63611458/attachment.html>