On Tue, 5 Mar 2013, Mattias Gaertner wrote:
Michael Van Canneyt <mich...@freepascal.org> hat am 5. März 2013 um 11:09
geschrieben:
On Tue, 5 Mar 2013, Sven Barth wrote:
Am 05.03.2013 10:58, schrieb Henry Vermaak:
On Tue, Mar 05, 2013 at 09:41:37AM +0000, Mark Morgan Lloyd wrote:
Sven Barth wrote:
Am 05.03.2013 10:14, schrieb Mark Morgan Lloyd:
But on the other hand, if an application programmer could
disable FPC's unit handling and use make -j instead, choosing
to pay the price of difficult maintenance, it might defuse the
criticism coming from certain quarters.
Make can not figure out the dependencies between units by itself
as it would need to parse them.
That's for the user to do, if he thinks he can do a better job than FPC.
Or implement an option that spits out the dependencies for make, so that
the user doesn't have to do this.
As this is something we (as in the FPC developers) don't need: patches are
welcome.
[or you could try whether the ppdep tool still works:
http://www.freepascal.org/tools/ppdep.var ]
There is a new tool "pas2fpm.pp" which can easily be adapted to do this.
It already calculates the dependencies, but outputs them in fpmake form.
Is this correct:
You need the tool pas2fpm to feed the tool fpmake to feed the tool fpc to feed
linker, lazres ....
You don't need anything. You can create fpmake.pp yourself.
pas2fpm makes it easier for you.
Just like "configure" and "autoconf" make it easier to create Makefiles if you
use C.
But because pas2fpm parses your units to do its job, it can go wrong, even on
legal code.
So using it should be optional.
You could try and integrate all in 1 tool (like in an IDE as lazarus).
fpmake was set up so it can be integrated completely in lazarus if you want it.
Same for fppkg.
Michael.
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
