Changes between Version 23 and Version 24 of DevelopingSymbianAppWithCarbide

Timestamp:

Dec 31, 2007 9:47:04 AM (16 years ago)

Author:

bennylp

Comment:

--

DevelopingSymbianAppWithCarbide

@@ -390 +390 @@
 Sometimes Carbide does not build the project properly after we make some changes to the source. This will cause the old code to be built instead of the new changes.
 
-My solution is to always clean the project before building it, to make sure that the modified libraries/application gets rebuilt properly.
+My standard work flow is to always clean the library/application project containing the modified source before building the whole project, to make sure that the modified libraries/application gets rebuilt properly.
+
+
+=== I/O Error: File in Use ===
+
+Sometimes .SIS creation fails with I/O error message in the ''Problems'' pane similar to this message:
+
+{{{
+file I/O fault
+makesis.exe returned with exit value == 1
+The process cannot access the file because it is being used by another process.
+}}}
+
+First check that the build process has completed without errors (a build error will cause the executable not to get built, and this will cause .sis creation to fail). 
+
+If the build process completes successfully but the .SIS creation still complains about file in use, restart Carbide C++. That should fix it.
 
 
@@ -400 +415 @@
 
 I'm not sure what's causing this, but closing TRK on the phone, then reconnecting the USB cable and restarting TRK seems to have fixed this.
+
+=== TRK Not Running Error ===
+
+Sometimes I get Carbide complaining about TRK not running:
+
+{{{
+Launching
+
+Target request failed: TRKProtocolPlugin: Can't connect to TRK
+(TRK may not be running on the phone or mismatch between selected and
+connected com port.).
+}}}
+
+Like this dialog:
+
+[[Image(trk_not_running.JPG)]]
+
+If you see TRK is running on the phone, it means that your phone is hung now. Restart the phone by disconnecting the USB cable, taking of the battery, put it back on, start the phone, connect the USB cable, and re-run TRK again.