Sign in Join

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

Mailing lists / fpc-pascal / 2007-07

fpc make vs. gnu make

5 messages · 5 people · –

Reply by email Subscribe to this list Your subscription

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

Tom Walsh

I am starting work on one fpc project and planning another. The current project will be for an x86 target, the planned project would be on ARM. I'm confused by the inclusion of a make utility within the fpc package.

Is there a compelling reason NOT to use GNU make for the fpc projects? Is there any benefit to the fpc make?

Regards,

TomW

Tom Walsh - WN3L - Embedded Systems Consultant http://openhardware.net http://cyberiansoftware.com http://openzipit.org "Windows? No thanks, I have work to do..." ----------------------------------------------------

Reply by email

Michael Van Canneyt
to Tom Walsh: I am starting work on one fpc project and planning another. The current project will be…
Tom Walsh wrote 6 lines
I am starting work on one fpc project and planning another. The current project will be for an x86 target, the planned project would be on ARM. I'm confused by the inclusion of a make utility within the fpc package. Is there a compelling reason NOT to use GNU make for the fpc projects? Is there any benefit to the fpc make?

The FPC provided make is GNU make.

Michael.

Reply by email

Tomas Hajny
to Michael Van Canneyt
Michael Van Canneyt wrote 12 lines
On Thu, 12 Jul 2007, Tom Walsh wrote: > I am starting work on one fpc project and planning another. The current > project will be for an x86 target, the planned project would be on ARM. > I'm > confused by the inclusion of a make utility within the fpc package. > > Is there a compelling reason NOT to use GNU make for the fpc projects? > Is > there any benefit to the fpc make? The FPC provided make is GNU make.

@Michael: He probably means fpcmake.

@Tom: fpcmake isn't used for building but rather for construction and maintenance of proper Makefile (later executed by GNU make) from simplified Makefile.fpc allowing not to repeat platform specific knowledge and focus just to stuff need for building Pascal units and programs (in this context, you could compare it to autoconf known in the C world).

However, because of limitations of GNU make, especially talking about some less common platforms, it's intended to avoid need of GNU make altogether and replace it with the new fppkg system (this is only for the future, though, not in use yet).

Tomas

Reply by email

Marco van de Voort
to Florian Klaempfl: Main problem: you can't express the cyclic interdependencies pascal units can have.
Show quoted text 5 lines
Tom Walsh schrieb: > Is there a compelling reason NOT to use GNU make for the fpc projects? Main problem: you can't express the cyclic interdependencies pascal units can have.

- Having to ship an external binary (or on *nix lay a dependancy).
- Expansion (more syntax/commands) mostly via external programs. An own product can simply integrate required functionality.
- Still needs an external tool (fpcmake) to generate the makefile, since the basic makefile syntax is not abstract enough.
- Only old or bad quality builds available on non *nix. (Windows is ok though nowadays)
- Integrating support for future expansions (like more complex library support) would complicate the current generator (and resulting files) even futher.
- GNU.

Reply by email