@Thaddy: that's contradicting. If I rename a file that belongs to Lazarus itself, I probably cannot compile Lazarus any more. If I cannot compile Lazarus any more, I can't compile my own extension into Lazarus
I know about resource compiling, and the laz_images_list.txt file is merely a list of filenames. Plus, that would be exactly the same problem - I would need to point to the Lazarus folder, without knowing where the user had installed Lazarus
I could pick, from any generated .gdb, the path to one of the LCL units, construct the Lazarus path from there, and then load the image resources there. But that's looks way too complicated compared to simply copying the file (or using different icons).
@marcov: thanks for clarifying the relativity of the path! Sorry for misunderstanding this earlier
I'll see if this helps. I noticed that in the subversion trunk, the FPC directory lies parallel to the Lazarus directory, while in releases, it's a subfolder of it.
{$R ResFolder\laz_images.res} does not work (regards ResFolder as part of the path), but I'll play around with that as well