Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-pascal / 2025-05

How to make all FPC utils?

4 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Thomas Kurz

Hello,

I'm trying to create an automated dockerized build of FPC targeting Win32 (and later Win64). Everything's fine so far, except the `utils` directory.

My `make` command is `make clean all FPC=/usr/lib/fpc/3.2.2/ppcross386 OS_TARGET=win32 CPU_TARGET=i386`.

When I run this, e.g. in the `utils/fpcm`, I get:

./fpmake clean --localunitdir=../.. --globalunitdir=../../packages --os=win32 --cpu=i386 -o -Twin32 -o -Pi386 -o -XPi386-win32- -o -Xr -o -di386 --compiler=/usr/lib/fpc/3.2.2/ppcross386 -bu ./fpmake compile --localunitdir=../.. --globalunitdir=../../packages --os=win32 --cpu=i386 -o -Twin32 -o -Pi386 -o -XPi386-win32- -o -Xr -o -di386 --compiler=/usr/lib/fpc/3.2.2/ppcross386 -bu Start compiling package utils-fpcm for target i386-win32. Subversion executable (svn) not found. Svn-revision in fpcmake executable might be out of date. Compiling BuildUnit_utils_fpcm.pp
Compiling fpcmmain.pp
Compiling fpcmdic.pp
Compiling fpcmwr.pp
Compiling fpcmpkg.pp
Compiling fpcmake.pp
Linking bin/i386-win32/fpcmake.exe
[100%] Compiled package utils-fpcm

However, making in `utils` leads to (only the "fpcm" subsection):

Start compiling package utils-fpcm for target i386-win32. Subversion executable (svn) not found. Svn-revision in fpcmake executable might be out of date. Compiling fpcm/BuildUnit_utils_fpcm.pp
Compiling fpcm/fpcmmain.pp
Compiling fpcm/fpcmdic.pp
Compiling fpcm/fpcmwr.pp
Compiling fpcm/fpcmpkg.pp
[ 14%] Compiled package utils-fpcm

You see that compilation of `fpcmake.pp` is missing, thus `fpcmake.exe` is missing, too.

What am I doing wrong?

Kind regards,
Thomas

Reply by email

Marco van de Voort
to Thomas Kurz

Op 22-5-2025 om 10:16 schreef Thomas Kurz via fpc-pascal:

I'm trying to create an automated dockerized build of FPC targeting Win32 (and later Win64). Everything's fine so far, except the `utils` directory.

Pass FPCMAKENEW=/path/to/utils/fpcm/bin/i386-win32/fpcmake.exe correct the path to generated make.

I, however,  only have  done this with trunk, don't know if it works with 3.2.2.

Reply by email

Thomas Kurz
to Marco van de Voort
Pass FPCMAKENEW=/path/to/utils/fpcm/bin/i386-win32/fpcmake.exe correct

the path to generated make.

I must admit I don't understand this response. First thing is I'm on Linux x64 and I don't think that the `fpcmake.exe` will help. Apart from that, there *is* an fpcmake built just some minutes ago which is being used.

My problem is just that I *can* `make` all utilities, but I have to `chdir` into each separately. On the other hand, there is a makefile in the parent directory which compiles lots of units, but just doesn't output any binaries (except for some pas2js, iirc). Is this behavior intentional?

Kind regards,
Thomas

Reply by email

Michael Van Canneyt
to Thomas Kurz
Thomas Kurz wrote 10 lines
> Pass FPCMAKENEW=/path/to/utils/fpcm/bin/i386-win32/fpcmake.exe correct the path to generated make. I must admit I don't understand this response. First thing is I'm on Linux x64 and I don't think that the `fpcmake.exe` will help. Apart from that, there *is* an fpcmake built just some minutes ago which is being used. My problem is just that I *can* `make` all utilities, but I have to `chdir` into each separately. On the other hand, there is a makefile in the parent directory which compiles lots of units, but just doesn't output any binaries (except for some pas2js, iirc). Is this behavior intentional?

It is not intentional.

If I run "make" in the utils/ directory, then all util programs are made.

Michael.

Reply by email