Re: igc: trying to chase a crash

[Andrea Corallo <acorallo@gnu.org>]

Gregor Zattler <telegraph@gmx.net> writes:

> Dear Andrea, Gerd, ...
> * Andrea Corallo <acorallo@gnu.org> [2024-11-27; 03:52 -05]:
>> Sure if it's of interest: my idea of few things that helped a lot native
>> comp in gaining traction at time:
>>
>> - publishing simple blog posts summarizing and explaining the progresses
>>   of the branch [1]
>
> Data Point: That got me interested.
> There were progress updates, so I
> visited the age rather often.
>
>> - native-comp being a feature branch, this clarified that the goal was
>>   merging to master (IOW something which was probably likely to happen)
>>   and that the branch was trackable by users.  That's why I suggested
>>   more than once this solution in the past.
>
> That and the instructions on how to use
> it motivated me to try out.
>
> In case of igc detailed build
> instructions would be needed (for me at least).

Yeah that's a great point!  For me building igc was not trivial.  MPS
doesn't come with distros and the experience of compiling it from source
wasn't great, the instructions in the codebase were conflicting plus I
had to manually patch the codebase as OOB was not compiling.  Finally
Emacs has to find it during compilation, otherwise I think it will
silently revert to the standard GC even if configured for it.

Maybe some of this is fixed now I'm not sure, but these are all hard
barriers for users, clear and detailed instructions would be much needed
for a more spread use of it.

  Andrea