makefiles
lazarus / 64-FPC development

----------------------------------------------------------------------
Key-Real · 2026-02-12 07:50

Hi,

do our BuildSystem regens make files on FPC Trunk compilation process?

I mean from Makefile.fpc

If not why?
We can trow all makefiles out of the repo, it would be cleaner.

----------------------------------------------------------------------
marcov · 2026-02-12 08:30

No it doesn't regen every time.

It would slow, and would increase bootstrap requirements, adding the
makefile generator to the minimal set of files needed.

----------------------------------------------------------------------
Key-Real · 2026-02-12 08:43

well now we are in a pickle.

my commit include regenerated makefiles because I excluded packages
for my target.

slowing down the build process is not a creterium, it takes a bit
now... so 4 sec would'nt be a havy deal.

I strongly recommend to regen them on the build process.

----------------------------------------------------------------------
Key-Real · 2026-02-12 09:04

now after every fork update I have to rebuild all makefiles and push a
new, only with the makefiles, commit to merge

----------------------------------------------------------------------
PascalDragon · 2026-02-12 20:32

Quote from: Key-Real on February 12, 2026, 09:43:45 amI strongly
recommend to regen them on the build process.
No, because the makefiles need to be regenerated using an fpcmake
built from the up to date version. So there would be the problem that
this would need to be built first, but that might depend on code only
available in the up to date RTL. So you'd have to rebuilt everything
anyway.

Quote from: Key-Real on February 12, 2026, 10:04:55 amnow after every
fork update I have to rebuild all makefiles and push a new, only with
the makefiles, commit to merge

That's simply how it is when you have a pending change for the
template.

----------------------------------------------------------------------
Key-Real · 2026-02-12 20:56

Quoteusing an fpcmake built from the up to date versionah, than ok. I
thought we use the Stable Version fpcmake

----------------------------------------------------------------------
PascalDragon · 2026-02-12 22:37

Quote from: Key-Real on February 12, 2026, 09:56:26 pmQuoteusing an
fpcmake built from the up to date versionah, than ok. I thought we use
the Stable Version fpcmake

No, because then targets only supported by main wouldn't be supported
like - tadda! - your PS1 port

----------------------------------------------------------------------
valdir.marcos · 2026-02-16 10:24

Quote from: PascalDragon on February 12, 2026, 09:32:43 pmQuote from:
Key-Real on February 12, 2026, 09:43:45 amI strongly recommend to
regen them on the build process.No, because the makefiles need to be
regenerated using an fpcmake built from the up to date version. So
there would be the problem that this would need to be built first, but
that might depend on code only available in the up to date RTL. So
you'd have to rebuilt everything anyway.

Quote from: Key-Real on February 12, 2026, 10:04:55 amnow after every
fork update I have to rebuild all makefiles and push a new, only with
the makefiles, commit to merge That's simply how it is when you have a
pending change for the template.Good information.