[fpc-devel] build process of official releases (3.0 / win)
fpc at mfriebe.de
Fri Dec 11 19:53:45 CET 2015
Someone pointed out that the official build and the 3.0 included in
Of course this can easily be caused by different OPT= specified. Not
sure what else may have an impact.
Starting compiler? Afaik should not, that is why there are 3 cycles?
Looking at the Lazarus build it seems that the compiler is build with no
OPT added at all.
Then some units are rebuild with smart-linking.
> %MAKEEXE% clean PP=%RELEASE_PPC% >> %LOGFILE% 2>&1
> %MAKEEXE% compiler_cycle PP=%RELEASE_PPC% >> %LOGFILE% 2>&1
> FOR /F %%L IN ('%SOURCE_DIR%\compiler\utils\fpc.exe -PB') DO SET
> FOR /F %%L IN ('%COMPILER% -iV') DO SET FPCVERSION=%%L
> FOR /F %%L IN ('%COMPILER% -iW') DO SET FPCFULLVERSION=%%L
> %MAKEEXE% rtl_clean PP=%COMPILER% >> %LOGFILE%
> %MAKEEXE% rtl packages PP=%COMPILER% OPT="-Ur -CX" >> %LOGFILE%
> %MAKEEXE% utils PP=%COMPILER% OPT="-CX -XX -Xs"
> DATA2INC=%SOURCE_DIR%\utils\data2inc >> %LOGFILE%
What options are specified for the release by fpc?
More information about the fpc-devel