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
On 22-4-2022 14:41, Marc Weustink via fpc-devel wrote:
OK, stash pop. You would think th
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
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
On 22-4-2022 10:09, Marc Weustink via fpc-devel wrote:
On 22-4-2022 09:55, Mar
On 22-4-2022 09:55, Marco van de Voort via fpc-devel wrote:
On 22-4-2022 09:12, Marc Weustink via fpc-devel wrote:
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
On 22-4-2022 09:12, Marc Weustink via fpc-devel wrote:
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 ca
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) C
