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

[Michael Van Canneyt]

On Fri, 4 Sep 2015, Paul Gevers wrote:

> Hi,
>
> On 04-09-15 23:07, Abou Al Montacir wrote:
>> On Fri, 2015-09-04 at 13:42 +0200, Paul Gevers wrote:
>>> Hi all,
>>>
>>> Apart from updating the d/copyright file I am close to ready with 3.0.0rc1.
>>>
>>> However, two details that I like your opinion on (especially with Abous
>>> knowledge):
>>> 1) there are multiple new binaries¹. Do we want to ship them all? I
>>> guess we do, but they all are missing man pages and their help isn't
>>> very good typically.
>> Yes, generally we want to provide all binaries. As a first step we can just
>> generate man pages from the help what ever the quality is. Then we can improve
>> that while the package is waiting in NEW.
>>> 2) There are multiple new files in
>>> usr/lib/fpc/3.0.0/fpmkinst/x86_64-linux/ all with the extension .fpm
>>> (fpmake files). Should they be shipped, are they useful after the build?
>> I suppose yes.
>> I'm not very knowledgeable about fpmake but I suppose that users who want to use
>> fpmake with some packages will need them. I'm here thinking about .lpk for
>> Lazarus. I think .fpm and .lpk are quite similar in the concept, but not the
>> implementation. But this is a pure speculation.

.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.

>>
>>> ¹ 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

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.

>
> 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

Michael.