Changes between Version 70 and Version 71 of Docs/825gen2/Dev/UpdatingLegacyApps

Timestamp:

02/19/25 15:02:41 (4 days ago)

Author:

Don Wilson

Comment:

--

Docs/825gen2/Dev/UpdatingLegacyApps

@@ -49 +49 @@
 20. Click "Apply and Close".
 
-21. Also create a "Release" build. Repeat the steps above from step 4, except name the build configuration "Release-ARM825" and copy the configuration from the "Release" build configuration. For the "Library search path" standard libraries change them to "Release-ARM825". The debug build will output messages from DEBUG_MSG statements in the code on the console. These messages are useful for debugging. These messages will be left out when the release build is compiled. The release build executable will often be a smaller size file and may have improved speed. The release build must also be tested as it is possible for problems to only show up in a release build. The build event for the signature file should also be modified for the release build to run "appsign64" to create the signature file.
+21. Also create a "Release" build. Repeat the steps above from step 4, except name the build configuration "Release-ARM825" and copy the configuration from the "Release" build configuration. For the "Library search path" standard libraries change them to "Release-ARM825". The debug build will output messages from DEBUG_MSG statements in the code on the console. These messages are useful for debugging. These messages will be left out when the release build is compiled. The release build executable will often be a smaller size file and may have improved speed. The release build must also be tested as it is possible for problems to only show up in a release build. 
+
+The "Post-build" step for the signature file should also be set or modified for the release build to run "appsign64" to create the signature file so that the app will show as a legitimate app in the application menu.
 
 [[Image(825gen2_buildsignature.png)]]