[Pkg-pascal-devel] [Core] fpc 3.0.0~rc1

[Abou Al Montacir]

Hi Michael,

Thank you for these highlights, it makes it easier to understand.

On Sat, 2015-09-05 at 13:46 +0200, Michael Van Canneyt wrote:
> 
> On Fri, 4 Sep 2015, Paul Gevers wrote:
...
> .fpm is only needed if you want to use fpmake. It is not similar in concept
> to .lpk, fpmake.pp is similar in concept to fpc. 
> .fpm is more similar in concept to the .compiled file that lazarus makes.
Thanks for this clarification. This makes it easier to understand what those
files are.
As the .compiled file are packaged, I assume then .fpm shall be too.
We shall allow users who want to use fpmake to do so.

> >>
> >>> ¹ cldrparser, fpcjres, mkarmins, mkinsadd, mkx86ins, pas2fpm, pas2jni,
> >>> pas2ut, unihelper
> 
> I am not sure that all these files should be installed to an end-user system.
> 
> - mkinsadd has no use except when you want to make a FPC installer on non
> -unices.
> - cldrparser is for internal use only, to create unicode tables.
> - unihelper is for internal use only, to create unicode tables.
> - mkarmins is only useful if you want to work on the compiler.
> - mkx86ins: same as mkarmins
According to this description we don't need them, however in the past some users
complained about missing binaries. I'd recommend that we skip them for now and
if anyone complains we can ask for man pages and add them later.

> I can make manual pages for fpcjres, pas2fpm, pas2jni, pas2ut
> But for the above, I really don't see the point as I don't think 
> they should be installed to begin with.
Ok let's do so. We install only these programs and the others not.
When do you think you can provide man pages for these? Just to see if we upload
without or we wait for you. In deed the first upload of any FPC release goes
through the NEW queue and takes a while. So we prefer to go as fast as possible
to this NEW queue.

> >
> > And I just found an other "issue". In the install directory there are
> > three java jar files. Two I believe are in principle available in Debian
> > (albeit maybe missing required patches) but the third one is I believe
> > FPC specific. However, until now I could find how to generate this from
> > the source (and I think that is not built by default). Investigating
> > further.
> 
> javapp converts a .class file to a .pas import declaration. you can find 
> sources in utils/javapp.
> jasmin is an external existing java bytecode assembler tool, but which needs 
> patches to be able to
> correctly process bytecode generated by fpc. 
> bcel can be used to analyse bytecode.
> 
> More info can be found at:
> http://wiki.freepascal.org/FPC_JVM
> http://wiki.freepascal.org/FPC_JVM/Usage
> http://wiki.freepascal.org/FPC_JVM/Language
> 
> or
> http://wiki.freepascal.org/Category:JVM
Then the jasmin-sable package shall be modified as we can not use external
binary as per Debian policy.
Are these patches available? Were they proposed to upstream? Shall we try to ask
Debian to include them while waiting for upstream to accept them?
-- 
Cheers,
Abou Al Montacir