Changes between Version 73 and Version 74 of Docs/825gen2/Dev/UpdatingLegacyApps

Timestamp:

02/19/25 15:24:54 (3 days ago)

Author:

Don Wilson

Comment:

--

Docs/825gen2/Dev/UpdatingLegacyApps

@@ -51 +51 @@
 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.
+22. 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)]]
 
-22. A few source code changes may be needed for proper operation on the 825 Gen2. If the app has USB import/export features it may use a fixed path "/mnt/fl1" for the USB drive. The USB drive path will not be the same on the 825 Gen2. Search the project for the string "/mnt/fl1" to find any code that should be changed. The library lib825ev has a function called [wiki:Docs/Prog/Manual/ApplicationLibraries/lib825ev/File/FindFlashDrive FindFlashDrive] for the 825 Gen2 to get the path string. The path may be similar to "/run/media/sda1" but it is best to use the !FindFlashDrive function instead of a hard coded path.
+23. A few source code changes may be needed for proper operation on the 825 Gen2. If the app has USB import/export features it may use a fixed path "/mnt/fl1" for the USB drive. The USB drive path will not be the same on the 825 Gen2. Search the project for the string "/mnt/fl1" to find any code that should be changed. The library lib825ev has a function called [wiki:Docs/Prog/Manual/ApplicationLibraries/lib825ev/File/FindFlashDrive FindFlashDrive] for the 825 Gen2 to get the path string. The path may be similar to "/run/media/sda1" but it is best to use the !FindFlashDrive function instead of a hard coded path.
 
-23. Also (probably rare) if the app communicates with another system by serial port, network, or file import/export that interprets the data content as binary integers, floats, etc... it may be necessary to make changes to account for different [https://en.wikipedia.org/wiki/Endianness endianness]. The 825 Gen2 is ARM-64 little-endian, The Legacy 825 is Coldfire big-endian. 
+24. Also (probably rare) if the app communicates with another system by serial port, network, or file import/export that interprets the data content as binary integers, floats, etc... it may be necessary to make changes to account for different [https://en.wikipedia.org/wiki/Endianness endianness]. The 825 Gen2 is ARM-64 little-endian, The Legacy 825 is Coldfire big-endian. 
 
-24. In the /srv/nfs/arm825/mnt/nand/apps/<projectname> directory it is helpful to create a script "mktgz.sh" to generate a release package to give to customers to install the app. 
+25. In the /srv/nfs/arm825/mnt/nand/apps/<projectname> directory it is helpful to create a script "mktgz.sh" to generate a release package to give to customers to install the app. 
 {{{
 #!/bin/sh