On 10/24/2014 12:39 AM, Jonas Maebe wrote:
On 23/10/14 17:16, Vsevolod Alekseyev wrote:
There's no separate makefile for fpcmake alone, is there?
It used to be as simple as going into utils/fpcm and performing a "make
all", but with the new FPC-based build system I think that is
unfortunately no longer possible.
With the fpcmake-buildsystem it was possible to build one package from
fpc-trunk using a fpc-release-compiler with a simple "make all". But the
release-version of all dependencies were used.
So when fpcm-trunk uses a new feature in trunk-fcl-base, there was no
way to compile the trunk-version of fpcm with a release-compiler.
With fppkg this all changed. Now it's always possible to compile
(single) trunk-packages using the latest release-compiler. The command
has been altered, though. You have to do 'fppkg build', instead of 'make
all'. Fppkg will then compile all the packages that fpcm depend on using
the new compiler.
This does not work if the new fpcm-package uses new compiler features
offcourse. And the same holds for the rtl because that one is still
compiled using the fpcmake-system.
There's one problem, still, and that's the same problem you have with
the fpcmake-system. When the Makefile's do not support a new target, you
have to re-generate those first using a new version of fpcmake.
The same holds with the fpmake-system. When your fpmake uses some new
functionality that is only available in the new compiler or a new
fpmkunit-unit, you have a problem. For this case fppkg uses two
configurations. One to compile the fpmake.pp-files, and one to compile
the actual packages. But that's not configured by default.
Joost.
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
