| Re: [hatari-devel] Upstream / downstream code in Hatari |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: Eero Tamminen <oak@xxxxxxxxxxxxxx>, Hatari devel list <hatari-devel@xxxxxxxxxxxxxxxxxxx>
- Subject: Re: [hatari-devel] Upstream / downstream code in Hatari
- From: Andreas Grabher <andreas_g86@xxxxxxxxxx>
- Date: Fri, 22 Aug 2025 07:15:09 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=1a1hai; bh=3H7q4MwLOcTb+hYhRL4CFSa0UUMGIEd5xP01Lb9Bs20=; h=Content-Type:From:Mime-Version:Subject:Date:Message-Id:To:x-icloud-hme; b=daQUmHrSi2OUb+zL0Xe15Bgiu6uoYa5bR/eJxPj1GOINvCS2Hmi5Fxq/zeub/g8HrUli/qWX1NRsaWi1gLeSn5YcvAQZW7DleN2zckmCb8DzYc9XWqGEmRt2bDWW+60o9YhWHA/an0hyYeW4aioog0z0WACEPahTciVMLrbpQjMJrW66SnL1Pi/O/EiNG4DRcelpnuLKMOjXfsjpFJyh5yJ2us4LLS+DSK3jTELidiZCh15b+rf+4iNLUqKAxVVoNY2DOfp2qZsMNgHrmqZZ70r426CpYKMf6mwGyoF5IWTZsHlz3MB4eM4DKOnmRpHC/xRmHNu4xXIynTCy8BgfPg==
> Out of curiosity, do you build src/cpu/ with WINUAE_FOR_HATARI enabled?
>
Yes, but some of those code parts are disabled afterwards.
> You don't have any need for profiling or debug symbols and backtraces (which needs both of those functionalities)?
>
> I don't think profiler has anything Atari specific except handling and printing of memory area limits, which is very small part of it.
>
> It needs symbols though, but while binary symbol formats are Atari specific, the ASCII one (used with profile post-processor) is not, and I think you can just ignore (ifdef out) rest.
>
I don‘t use profiling and also the debugger is not really in use by me. Therefore I did not invest too much time into that part. But I would like to keep the option to add this later.
> I would guess that NeXT users don't use fsel ZIP browsing functionality that much. It's been there long time, but I'm not sure whether I've never used it myself, as all my (floppy) image files are separate.
>
I agree. This may be removed on Previous. But then it would cause more extra differences in the GUI code. That is one example of where interconnecting different code parts leads to restrictions.
> NeXT supports just 7-bit ASCII file names and does not need conversion of 8-bit characters?
>
Good question. Everything seems to work so I didn‘t care for that.
> Applying each relevant commit from Hatari sources by hand, sounds rather laborious.
>
> But with this large set of differences, handling git rebase conflicts could also be quite a lot of work, especially when list of change commits stacked on top of the upstream code grows (so at some point it would be more work unless those changes could be upstreamed).
>
That is exactly the problem. Therefore I am interested in keeping the differences small. It is not that big of a problem if a file contains Atari specific parts concentrated at the bottom and common parts on top. But it gets annoying if everything is mixed up and new dependencies are added.
> What version control you're using for Previous code?
>
I use subversion.
Andreas