Recent changes to Linking error E2597

Linking error E2597 modified by Arnold Reinders

Arnold Reinders — Wed, 30 Oct 2013 17:31:51 -0000

--- v4
+++ v5
@@ -16,6 +16,6 @@
       not this                          but this
       TMandel_View = class (TObject)    TMandel_View = class (TObject)
          FStop_Watch: TStopWatch;       private // all is ok except published
-                                         FStop_Watch: TStopWatch; 
+                                           FStop_Watch: TStopWatch;

 [Back](https://sourceforge.net/p/multimandel/wiki/Mission%20statement/)

Linking error E2597 modified by Arnold Reinders

Arnold Reinders — Wed, 30 Oct 2013 17:31:24 -0000

--- v3
+++ v4
@@ -7,23 +7,15 @@

 1. Remove all object files. These can be found in \Android\Debug (or release). Remove all files, except directories. Usually this works.

-2. Inspect very carefully your function definitions and calls and make sure you use the exact types. In one case the error disappeared 
+2. Inspect very carefully your function definitions and calls and make sure you use the exact types. In one case the error seems to be caused because the header contained and `integer` while the function was called with a `uInt32`.

-3. Have the compiler emitting RTTI information. Go to Project | Compiling | Emit runtime type information. When you get lots of the following errors:
+3. Have the compiler emitting RTTI information. Go to Project | Compiling | Emit runtime type information. When you get lots of E2217 compiler errors make sure that your class does not use `published` as an access specifier for that field but use another one like private, protected or public.

-    [dcc32 Error] Mandel_View.pas(36): E2217 Published field 'FStop_Watch' not a class or interface type
+-

-That happened in a class declared as follows:
-
-    TMandel_View = class (TObject)
-       FStop_Watch: TStopWatch;
-
-This time the Embaracdero help *was* helpful and I learned that I had probably omitted a private statement. Changing the code to
-
-    TMandel_View = class (TObject)
-    private // all is ok except published
-       FStop_Watch: TStopWatch;
-
-helped. No more compiler errors and code that compiled without problems to Android.
+      not this                          but this
+      TMandel_View = class (TObject)    TMandel_View = class (TObject)
+         FStop_Watch: TStopWatch;       private // all is ok except published
+                                         FStop_Watch: TStopWatch; 

 [Back](https://sourceforge.net/p/multimandel/wiki/Mission%20statement/)

Linking error E2597 modified by Arnold Reinders

Arnold Reinders — Wed, 30 Oct 2013 17:17:49 -0000

--- v2
+++ v3
@@ -3,7 +3,13 @@

 This is a most baffling error as it occurs during linking code for the Android target which ran flawlessly for the Win32 target. What happens is that the Android linker reports that some symbols were not found in the C++ code which was compiled from object Pascal. The code is clearly present in the Pascal code. Commenting out the code leads to another error in another part of the code. The linker is clearly bent upon your destruction. Or so it seems. The [Embarcadero](http://docwiki.embarcadero.com/RADStudio/XE4/en/E2597_%27%25s%27_%28Delphi%29) help is not the most useful in the world.

-Sometimes the error disappears after some tweaking in order to reappear after some other twiddling. I reasoned that this was probably due to a compiler/linker setting by emitting too few information to the linker. That saved my ink-black temper. Go to Project | Compiling | Emit runtime type information. I switched it on and lots of the following errors:
+There are several ways to get out of this situation.
+
+1. Remove all object files. These can be found in \Android\Debug (or release). Remove all files, except directories. Usually this works.
+
+2. Inspect very carefully your function definitions and calls and make sure you use the exact types. In one case the error disappeared 
+
+3. Have the compiler emitting RTTI information. Go to Project | Compiling | Emit runtime type information. When you get lots of the following errors:

     [dcc32 Error] Mandel_View.pas(36): E2217 Published field 'FStop_Watch' not a class or interface type

@@ -15,9 +21,9 @@
 This time the Embaracdero help *was* helpful and I learned that I had probably omitted a private statement. Changing the code to

     TMandel_View = class (TObject)
-    private
+    private // all is ok except published
        FStop_Watch: TStopWatch;

-was very helpful indeed. No more compiler errors and code that compiled without problems to Android.
+helped. No more compiler errors and code that compiled without problems to Android.

 [Back](https://sourceforge.net/p/multimandel/wiki/Mission%20statement/)

Linking error E2597 modified by Arnold Reinders

Arnold Reinders — Wed, 23 Oct 2013 19:25:38 -0000

--- v1
+++ v2
@@ -1,4 +1,5 @@
-###Linking error E2597###
+Linking error E2597
+----

 This is a most baffling error as it occurs during linking code for the Android target which ran flawlessly for the Win32 target. What happens is that the Android linker reports that some symbols were not found in the C++ code which was compiled from object Pascal. The code is clearly present in the Pascal code. Commenting out the code leads to another error in another part of the code. The linker is clearly bent upon your destruction. Or so it seems. The [Embarcadero](http://docwiki.embarcadero.com/RADStudio/XE4/en/E2597_%27%25s%27_%28Delphi%29) help is not the most useful in the world.

@@ -18,3 +19,5 @@
        FStop_Watch: TStopWatch;

 was very helpful indeed. No more compiler errors and code that compiled without problems to Android.
+
+[Back](https://sourceforge.net/p/multimandel/wiki/Mission%20statement/)

Linking error E2597 modified by Arnold Reinders

Arnold Reinders — Wed, 23 Oct 2013 19:21:35 -0000

Linking error E2597

This is a most baffling error as it occurs during linking code for the Android target which ran flawlessly for the Win32 target. What happens is that the Android linker reports that some symbols were not found in the C++ code which was compiled from object Pascal. The code is clearly present in the Pascal code. Commenting out the code leads to another error in another part of the code. The linker is clearly bent upon your destruction. Or so it seems. The Embarcadero help is not the most useful in the world.

Sometimes the error disappears after some tweaking in order to reappear after some other twiddling. I reasoned that this was probably due to a compiler/linker setting by emitting too few information to the linker. That saved my ink-black temper. Go to Project | Compiling | Emit runtime type information. I switched it on and lots of the following errors:

[dcc32 Error] Mandel_View.pas(36): E2217 Published field 'FStop_Watch' not a class or interface type

That happened in a class declared as follows:

TMandel_View = class (TObject)
   FStop_Watch: TStopWatch;

This time the Embaracdero help was helpful and I learned that I had probably omitted a private statement. Changing the code to

TMandel_View = class (TObject)
private
   FStop_Watch: TStopWatch;

was very helpful indeed. No more compiler errors and code that compiled without problems to Android.