[Lazarus] How to find error from 'Error compiling resources'?

[Sven Barth]

Am 18.04.2012 11:17, schrieb Giulio Bernardi:
> Il 18/04/2012 10.26, Sven Barth ha scritto:
>> Am 18.04.2012 10:14, schrieb Giulio Bernardi:
>>> Il 18/04/2012 9.38, Sven Barth ha scritto:
>>>> Am 18.04.2012 09:32, schrieb Mattias Gaertner:
>>>>> On Tue, 22 Nov 2011 06:20:39 +0800
>>>>> Paul Ishenin<webpirat at mail.ru> wrote:
>>>>>
>>>>>> 21.11.11 21:38, Mattias Gaertner wrote:
>>>>>>> > At the same time when you compile from the console you can read
>>>>>>> the
>>>>>>> > error message.
>>>>>>>
>>>>>>> Maybe the IDE stops reading the output on error and forgets to read
>>>>>>> the
>>>>>>> rest.
>>>>>>>
>>>>>>> Maybe the compiler shuts down, before the IDE can read everything.
>>>>>>>
>>>>>>> Is it possible to simulate the bug?
>>>>>>
>>>>>> Add {$R *.res} to the project file twice.
>>>>>
>>>>> It shows
>>>>>
>>>>> Compiling resource /path/test/lib/x86_64-linux/project1.or
>>>>> project1.lpr(19,1) Error: Error while compiling resources
>>>>>
>>>>> Is there some way to get some more information from the resource
>>>>> compiler?
>>>>
>>>> fpcres itself supports a "--verbose" command, but the compiler doesn't
>>>> pass this
>>>> to the tool. So you'd need to have a wrapper application/script which
>>>> passes
>>>> that parameter as well.
>>>
>>> Hello. IIRC, passing -v to the compiler also passes --verbose to fpcres,
>>> so a
>>> verbose fpc implies that fpcres is verbose too :)
>>
>> No, it does not. I looked at the source.
>
> Ops, you're right. I checked now and it is '-vd' (verbose with debug
> output)
> that passes -v to fpcres.

I also checked again. You are basically right, but only for those 
systems were winlike resource files are used (which are basically all 
systems natively supported by Lazarus, exceptions are for example DOS, 
OS/2, NativeNT, Haiku, BeOS and embedded targets (including NDS, GBA and 
Wii)).

Regards,
Sven