Hi *.*.

We use a recent Lazarus snapshot (Lazarus 0.9.31 r30406 FPC 2.4.3 i386-win32-win32/win64) for developing applications for a Windows Embedded CE 6.0.

After expanding one of the projects by adding another dialog, we got the above mentioned error message while linking. Normally we use the following settings:

-CX
-O1
-g
-gl
-Xs
-Xg

Even if we only added the new unit to the uses statement - Lazarus gave us the hint "unit not used" - we got this error. Compiling the project without the additional dialog we reach the following file sizes:

*.dbg 29.732 k
*.exe 4.870 k

If we replace another dialog with the new one the project compiled well, so the problem couldn't related to this specific dialog.

In order to compile the project with the new dialog we removed -g and -gl and got the following file sizes:

*.dbg 12.670 k
*.exe 4.864 k

Of course we are not able to debug the project any more.

Greetings

Link to the forum discussion on the same topic:
http://www.lazarus.freepascal.org/index.php/topic,12971.0.html

Björn Schreiber wrote

After expanding one of the projects by adding another dialog, we got the above mentioned error message while linking.

Really no hints? It starts driving me nuts that I can't debug our Windows CE project any more ...

Greetings

Does anyone know if we have our own internal linker to wince? It seams that yes, but I that's very strange for me. I thought that we have it only for x86-win32.

Felipe Monteiro de Carvalho wrote

Does anyone know if we have our own internal linker to wince? It seams that yes, but I that's very strange for me. I thought that we have it only for x86-win32.

We have it for all windows targets.

Best regards,
Paul Ishenin

What you can try is to compile the LCL without debug information (add the option -g- for the LCL compilation), and then compile your own program with debug information. You won't be able to step into the LCL, but debugging your own code may work again.

Jonas

Paul Ishenin wrote

We have it for all windows targets.

Interresting. In that case another possible solution is using an external linker instead, as pointed in the forum. One might need to link manually and maybe even build a newer linker from binutils sources.

Jonas Maebe wrote

What you can try is to compile the LCL without debug information (add the option -g- for the LCL compilation)

Thank you for your answer, I will give it a try.

Greetings