Sign in Join

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

Mailing lists / fpc-devel / 2015-12

multi version ppudump

5 messages · 3 people ·

Reply by email Subscribe to this list Your subscription

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

Mattias Gaertner

Hi,

Short:
The default install (e.g. make install and most installers) replaces the ppudump utility, reducing its usefulness. For example when Lazarus should support code navigation without sources it requires a working ppudump.

Long:
When installing a second version of FPC via 'make install' (and most installers) the ppc* binary is put into a versioned path (e.g. under Linux /usr/local/lib/fpc/<fpcversion>/). This allows to easily switch the compiler.
OTOH ppudump is installed in a non versioned path (e.g. Linux /usr/local/bin), so installing another FPC version replaces the ppudump binary.
I know it is possible to install it under a different path, but most users simply use the default.
It would be nice if the default would install a multi version ppudump, for example similar to fpc->ppc*.

Any ideas?

Mattias

Reply by email

Michael Van Canneyt
to Mattias Gaertner
Mattias Gaertner wrote 8 lines
Hi, Short: The default install (e.g. make install and most installers) replaces the ppudump utility, reducing its usefulness. For example when Lazarus should support code navigation without sources it requires a working ppudump.

Hm. ppudump should be backwards compatible ? Or at least, that was the original design ?

Show quoted text 14 lines
Long: When installing a second version of FPC via 'make install' (and most installers) the ppc* binary is put into a versioned path (e.g. under Linux /usr/local/lib/fpc/<fpcversion>/). This allows to easily switch the compiler. OTOH ppudump is installed in a non versioned path (e.g. Linux /usr/local/bin), so installing another FPC version replaces the ppudump binary. I know it is possible to install it under a different path, but most users simply use the default. It would be nice if the default would install a multi version ppudump, for example similar to fpc->ppc*. Any ideas?

This can be done, but not before 3.2...

Michael.

Reply by email

Mattias Gaertner
to Michael Van Canneyt
[...] Hm. ppudump should be backwards compatible ? Or at least, that was the original design ?

AFAIK it never supported older versions.

For example:
pascal/3.0.0/fpc/compiler/utils/ppudump -Fj /usr/lib/fpc/2.6.4/units/x86_64-linux/graph/ggigraph.ppu Unsupported PPU version 135. Expecting PPU version 172.

[...] This can be done, but not before 3.2...

Do you mean 3.2 or 3.1.1)?

Mattias

Reply by email

Michael Van Canneyt
to Mattias Gaertner
Mattias Gaertner wrote 11 lines
On Wed, 2 Dec 2015 16:49:30 +0100 (CET) Michael Van Canneyt wrote: > [...] > Hm. ppudump should be backwards compatible ? Or at least, that was the original design ? AFAIK it never supported older versions. For example: pascal/3.0.0/fpc/compiler/utils/ppudump -Fj /usr/lib/fpc/2.6.4/units/x86_64-linux/graph/ggigraph.ppu Unsupported PPU version 135. Expecting PPU version 172.

Strange; Originally it could handle any version, it was a tool independent of the compiler. I seem to remember some discussion which probably changed that.

Show quoted text 6 lines
> [...] > This can be done, but not before 3.2... Do you mean 3.2 or 3.1.1)?

The installer ? That will be done in 3.1.1 and backported to 3.2 So in user installations, it will not appear before 3.2...

Michael.

Reply by email

Sven Barth
to Michael Van Canneyt
"Michael Van Canneyt" wrote 10 lines
On Wed, 2 Dec 2015, Mattias Gaertner wrote: > On Wed, 2 Dec 2015 16:49:30 +0100 (CET) > Michael Van Canneyt wrote: > >> [...] >> Hm. ppudump should be backwards compatible ? Or at least, that was the

original design ?

Show quoted text 6 lines
> > > AFAIK it never supported older versions. > > For example: > pascal/3.0.0/fpc/compiler/utils/ppudump -Fj

/usr/lib/fpc/2.6.4/units/x86_64-linux/graph/ggigraph.ppu

> Unsupported PPU version 135. Expecting PPU version 172. Strange; Originally it could handle any version, it was a tool

independent of the compiler. I seem to remember some discussion which probably changed that.

The file format itself is backwards compatible regarding the entries (one can skip entries one does not know), but the entries themselves aren't necessarily extended in a backwards compatible way...

Regards,
Sven

Reply by email