Re: [fpc-devel] resources on non-windows platform

[Paul Ishenin]

21.11.2016 21:13, Anton Kavalenka wrote:
Is not the time came for own resource compiler for limited type of 
resources (BITMAP, CURSOR, MANIFEST, VERSIONINFO)?

It should not be a problem for a very limited syntax.

But if you look at what delphi resource compiler can do then you find a 
very hard to implement feature - "include directive" which allows to use 
macroses and constants from .pas, .h and .cpp files.


--
Best regards,
Paul Ishenin.
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] resources on non-windows platform

[Jonas Maebe]

Anton Kavalenka wrote:
> {$R script.rc srcipt.res}
> 
> This kind of resource management implies usage of windres (or any other
> RC script compiler)
> 
> With the crosscompilation things became funnier:
> 
> I can under Linux get win32 exe with mingw-windres
> 
> I can under Linux get Mach-O 32 exe with odcc-windres
> 
> I can NOT under MacOS get Mach-O 32/64 exe with resources.

Can't you just convert the the .rc file to .res (with windres on any
platform) and then let FPC convert the .res file to the appropriate
object format?

> Is not the time came for own resource compiler for limited type of
> resources (BITMAP, CURSOR, MANIFEST, VERSIONINFO)?

I would argue we already have plenty of things to maintain that are
tangential to the compiler itself. Additionally, while the above might
be enough for use case, it doesn't work to do this for a large and
generic project. We either do something well, or not at all.


Jonas
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] resources on non-windows platform

[Sven Barth]

Am 22.11.2016 08:04 schrieb "Anton Kavalenka" :
> So the question - why current FPC can link .res under any platform (with
the help of fpcres) but cannot build such file under any platform without
foreign tools?

Because there's no cross platform Pascal only tool for this.

> Is not the time came for own resource compiler for limited type of
resources (BITMAP, CURSOR, MANIFEST, VERSIONINFO)?

Patches welcome.

Regards,
Sven
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

[fpc-devel] resources on non-windows platform

[Anton Kavalenka]

Dear FPC-all!


I have a big projects with lots of DLLs. All of them are cross-platform 
and link the resources with $R directive.


For version info I use .rc scripts to manage it under VCS and to prevent 
.RES flicker under different compilers (FPC and Delphi)


Version info is a nice example.

{$R script.rc srcipt.res}

This kind of resource management implies usage of windres (or any other 
RC script compiler)


With the crosscompilation things became funnier:

I can under Linux get win32 exe with mingw-windres

I can under Linux get Mach-O 32 exe with odcc-windres

I can NOT under MacOS get Mach-O 32/64 exe with resources.

So the question - why current FPC can link .res under any platform (with 
the help of fpcres) but cannot build such file under any platform 
without foreign tools?


Is not the time came for own resource compiler for limited type of 
resources (BITMAP, CURSOR, MANIFEST, VERSIONINFO)?


with best regards,

Anton

___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel