[fpc-devel] GIT and binary files.

[Marco van de Voort]

Op 4-4-2026 om 18:58 schreef Graeme Geldenhuys via fpc-devel:
> As far as git is concerned, it should auto detect it as a binary.
>
Depending on EOL detection it seems. But this is a compield resource 
file which packs an manifest (XML) in it, so it naturally has EOLs in 
it, which is why I was careful.

Anyway after adding the explorer properties said something like 
"saveEOL: false" or something like that. I hope that means it is binary.

Thanks for some keywords to google.

> Binaries might be blocked though via the. gitignore file, in which 
> case you'll have to use the --force argument.
>
> A git config file can also define how file extensions should be 
> treated. I'm not near a computer to see what FPC Source repo has 
> configured.
>
In the toplevel .gitattributes (is that valid for the whole repo?), only 
basic source files seem to have an assigned filetype, rest is auto.

Anyway, it is committed, an unit that has a manifest that sets the 
default ANSI codepage to UTF8 on "modern" Windows (Win10 1905+ iirc (*)) 
when used. As a bypass it also enables WinNT LFN. (8192 character 
filenames), a much older Windows feature.

I've found that these manifests with Lazarus for the last 5 years (that 
can configure them in the application tab) to be very convenient. Both 
features are great for small utilities and buildscripts in Pascal.  It 
was time to have them also for demos and utils etc in the the FPC tree.

Note the heightened Windows requirement only exists if you USES this unit.

(*) IOW all officially installed versions of WIndows, and even older 
corporate versions that might use the paid Win10 life extension.