Hi,

On a project I'm working on I needed to refactor some units. After I finished, I got a linking error about a duplicate resource. Maybe accidentally a stale one got linked, so I removed 2 occurrences. And now the compiler complains it cannot find the resource.

The (edited) output:
(9022) Compiling resource C:\Users\marc\x\x_service.rc (9028) Calling resource compiler
"C:\lazarus\fpc\3.2.2\bin\x86_64-win64\windres.exe" with "--preprocessor=C:\lazarus\fpc\3.2.2\bin\x86_64-win64\cpp.exe --include C:\lazarus\fpc\3.2.2\bin\x86_64-win64\ -O res -D FPC -o C:\Users\marc\x\x_service.res C:/Users/marc/x/x_service.rc" as command line ...
Debug: parsing command line parameters
Debug: parsing parameter '-o'
Debug: parsing parameter '-a'
Debug: parsing parameter '-of'
Debug: parsing parameter '-v'
Debug: parsing parameter '@C:\Users\marc\x\x.reslst' Debug: parsing parameter 'C:\lazarus\lcl\units\x86_64-win64\cursors.res' Debug: parsing parameter 'C:\lazarus\lcl\units\x86_64-win64\btn_icons.res' Debug: parsing parameter
'C:\lazarus\lcl\units\x86_64-win64\dialog_icons.res' Debug: parsing parameter '.\lib\x86_64-win64\x_service.res' Debug: parsing parameter 'C:\Users\marc\x\x_service.res' Debug: parsing parameter 'x.res'
Debug: parsing parameter 'x_version.res'
Debug: target set to x86_64 - coff
Debug: finished parsing command line parameters
...
Debug: Trying to open file .\lib\x86_64-win64\x_service.res... Error: Can't open file '.\lib\x86_64-win64\x_service.res' C:\Users\marc\x\x.dpr(45,1) Error: (9029) Error while compiling resources (9015) Linking C:\Users\marc\x\x.exe
C:\Users\marc\x\x.dpr(45,1) Fatal: (10026) There were 1 errors compiling module, stopping
Fatal: (1018) Compilation aborted

As you see, x_service.res is build in C:\Users\marc\x. So my question is where does the line '.\lib\x86_64-win64\x_service.res' come from

(and I wonder how did it compile the past years)

Marc

Well that is duplicate obviously.

Maybe you did some manual cmdline build that left a .res in the working dir , and your project has a stale {$R *.res} in the .dpr ?

That was the original problem, so I removed the versions from both locations. In the output you see that the new version is build as 'C:\Users\marc\x\x_service.res'

the '.\lib\x86_64-win64\x_service.res' is not build, hence my question, why is it tried to link that one ?

Maybe you did some manual cmdline build that left a .res in the working dir , and your project has a stale {$R *.res} in the .dpr ?

I do have a {$R *.res}, iirc this should link x.res (which you can see in the files passed)

Marc

OK,
I stashed my changes and compiled the previous version of the software without problems. '.\lib\x86_64-win64\x_service.res' is not linked, so somewhere my changes have triggered it.

To be continued...

Marc

OK, stash pop. You would think the problems should be the back... Yes they are, only different:

Debug: parsing parameter 'x_service.res'
Debug: parsing parameter 'x_service.res'
Debug: parsing parameter 'x.res'
Debug: parsing parameter 'x_version.res'

x_service.res is added twice, now from the same location.

To be continued...

Solved....

One of the changes I made was a rename of the unit where the resource is included. And there was still one unit using the old name (and the old ppu/o could be found)

Sorry for the noise,
Marc