fpcres now supports compilation of RC files

[lucamar]

But is it possible to use fpcres as stand-alone, something like:

Code: Pascal  [Select][+][-]

1. fpcres myresource.rc

That will produce a myresource.res.

And so first produce the .res , and in code, just use:

Code: Pascal  [Select][+][-]

1. {$R *.res}

You can always add it as an "Execute before" command in the "Compiler Commands" options of the project but you need an fpcres able to deal with .rc files; the only thing the currently released version (2.0) is able to do is convert a .res, normally into .o to link into the executable.

And even with the newish one you need to set all those options, as you have already discovered

[Fred vS]

But is it possible to use fpcres as stand-alone, something like:

Code: Pascal  [Select][+][-]

1. fpcres myresource.rc

That will produce a myresource.res.

And so first produce the .res , and in code, just use:

Code: Pascal  [Select][+][-]

1. {$R *.res}

You can always add it as an "Execute before" command in the "Compiler Commands" options of the project but you need an fpcres able to deal with .rc files; the only thing the currently released version (2.0) is able to do is convert a .res, normally into .o to link into the executable.

And even with the newish one you need to set all those options, as you have already discovered

Hello Lucamar.

Indeed, I did try with fpcres from FPC 3.2.0 and FPC 3.2.1 but rc format is not recognized.

But the one from FPC 3.3.1 trunk is working perfectly.
Very great job Sven.

Fre;D

[PascalDragon]

OK, I get it, this works perfectly on Linux (note the last parameters):

Code: Pascal  [Select][+][-]

1. fred@fiens ~/l/lazpaint> fpcres /home/fred/lazpaint-master/lazpaint/lazpaint.rc -o lazpaint.res -of res

Yes, we've decided against enabling res output by default (or some auto magic) due to backwards compatibility.

[lucamar]

Yes, we've decided against enabling res output by default (or some auto magic) due to backwards compatibility.

But, what about .rc input? Is it also disabled unless an output format is set? 'Cause that would kind of defeat the purpose of the new feature  ... whatever that is

IMHO, when one adds a new input format one should also define a default output one for it, depending on the purpose of the tool. Since fpcres has 'most always been about creating an object for linking, it's understandable that res output be available only on demand, but the problem seems to be that there is no default support for rc input either.

I'm not criticizing or anything ... well, yes, a little, but in a good way: I just would like some gleaming on your thougths about it.

[marcov]

I tried on one of my RCs (which embed shader files as resource streams), and it gives an error.

call:   

Code: [Select]

fpcres shadersrc.rc -o shadersrc.res -of res
error:

Code: [Select]

#MAIN.RC(1:43): at "emptycirclevertex": syntax error
vertexemptycircle RCDATA emptycirclevertex.ssrc
                                          ^
that first line is as reproduced in the error :

Code: [Select]

vertexemptycircle RCDATA emptycirclevertex.ssrc
which puts a shader source file as rcdata stream with name/ident vertexemptycircle. Note that some paths have windows style quoting, but it doesn't even get there:

Code: [Select]

thefontmeta RCDATA "c:\candelasvn\candelatex\pic\fonts\arial.fnt"


[PascalDragon]

Yes, we've decided against enabling res output by default (or some auto magic) due to backwards compatibility.

But, what about .rc input? Is it also disabled unless an output format is set? 'Cause that would kind of defeat the purpose of the new feature  ... whatever that is

The compiler knows that it needs to pass -of res.

IMHO, when one adds a new input format one should also define a default output one for it, depending on the purpose of the tool. Since fpcres has 'most always been about creating an object for linking, it's understandable that res output be available only on demand, but the problem seems to be that there is no default support for rc input either.

That is not how the classes in fcl-res work. Multiple different kinds of inputs can be used and their corresponding reader class is determined based on the content and not based on the file extension. The RC reader however is essentially a catch-all reader, thus it must not be enabled by default.
And the output format of fpcres is by default the binary resource format for the target (e.g. ELF, COFF, etc.).

I tried on one of my RCs (which embed shader files as resource streams), and it gives an error.

Best put that in a bug report with an example that can be used to reproduce this.

[marcov]

Ok, if you don't immediately recognize it, it is a bug. Filed as 38228