Changes between Version 15 and Version 16 of Docs/825gen2/Dev/UpdatingLegacyApps


Ignore:
Timestamp:
02/08/24 10:33:54 (9 months ago)
Author:
Don Wilson
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Docs/825gen2/Dev/UpdatingLegacyApps

    v15 v16  
    775. There is now a duplicated build configuration. We will change this configuration to compile for the new 825.
    886. Right-click on the project and select "Properties...", Select "Settings" and "Tool Settings".
    9 7. Select "GCC C++ Compiler". The "Command:" will show "m68k-uclinux-g++". Change this to "aarch64-none-linux-gnu-g++". This changes the compiler to compile for the ARM64 architecture.
    10 8. Select "GCC C++ Linker". The "Command:" will show "m68k-uclinux-g++". Change this to "aarch64-none-linux-gnu-g++". This changes the linker to link the project for the ARM64 architecture. Linking is the process of combining the already compiled code modules and libraries to create the executable.
    11 9. In some cases the project may also have a "GCC C Compiler". If so change the command to "aarch64-none-linux-gnu-gcc".
    12 10. In some cases the project may also have a "GCC Assembler". If so change the command to "aarch64-none-linux-gnu-as".
    13 11. Click the "Build Artifact" tab. Change the output prefix to "/srv/nfs/arm825_nand/apps/". This is where the completed app will be placed. Using this path will make it easy to test from an SSH connection into the 825. The "test825" script will automatically mount and select this path.
    14 12. Click "Apply".
    15 13. Go back to "Tool Settings" and under "GCC C++ Compiler" select "Include paths". Click the green plus icon to add a path. Add the path "/opt/arm64include". If there is a "GCC C Compiler" section also add this path to the includes there.
    16 14. Under the "GCC C++ Linker" select "Libraries". Add the libraries "rt", "${UI_LIBS}" and "pthread".
    17 15. Under "Library search path". Edit existing library paths as appropriate. For example change "${workspace_loc:/lib825ev/Debug}" to "${workspace_loc:/lib825ev/Debug-ARM825}"
    18 16. Click the green plus icon and add the library path "/opt/arm64lib"
    19 17. Under "GCC C++ Compiler" select "Preprocessor". Click the green plus icon to add the symbol "ARM64=1" This is used for conditional compilation. If there is also a "GCC C Compiler" section select "Preprocessor under that and also add the symbol "ARM64=1".
    20 18. Click "Apply and Close".
    21 19. It is also recommended to create a "Release" build. Repeat the steps above from step 3, 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"
     97. Some projects might have "Cross Settings" under "Tool Settings". If so change the "Prefix" from "m68k-uclinux-" to "aarch-none-linux-gnu-" (Be the to not leave out the final minus sign). If the "Cross Settings" is in the project the following steps 8-11 may then be skipped.
     108. Select "GCC C++ Compiler". The "Command:" will show "m68k-uclinux-g++". Change this to "aarch64-none-linux-gnu-g++". This changes the compiler to compile for the ARM64 architecture.
     119. Select "GCC C++ Linker". The "Command:" will show "m68k-uclinux-g++". Change this to "aarch64-none-linux-gnu-g++". This changes the linker to link the project for the ARM64 architecture. Linking is the process of combining the already compiled code modules and libraries to create the executable.
     1210. In some cases the project may also have a "GCC C Compiler". If so change the command to "aarch64-none-linux-gnu-gcc".
     1311. In some cases the project may also have a "GCC Assembler". If so change the command to "aarch64-none-linux-gnu-as".
     1412. Click the "Build Artifact" tab. Change the output prefix to "/srv/nfs/arm825_nand/apps/". This is where the completed app will be placed. Using this path will make it easy to test from an SSH connection into the 825. The "test825" script will automatically mount and select this path.
     1513. Click "Apply".
     1614. Go back to "Tool Settings" and under "GCC C++ Compiler" select "Include paths". Click the green plus icon to add a path. Add the path "/opt/arm64include". If there is a "GCC C Compiler" section also add this path to the includes there.
     1715. Under the "GCC C++ Linker" select "Libraries". Add the libraries "rt", "${UI_LIBS}" and "pthread".
     1816. Under "Library search path". Edit existing library paths as appropriate. For example change "${workspace_loc:/lib825ev/Debug}" to "${workspace_loc:/lib825ev/Debug-ARM825}"
     1917. Click the green plus icon and add the library path "/opt/arm64lib"
     2018. Under "GCC C++ Compiler" select "Preprocessor". Click the green plus icon to add the symbol "ARM64=1" This is used for conditional compilation. If there is also a "GCC C Compiler" section select "Preprocessor under that and also add the symbol "ARM64=1".
     2119. Click "Apply and Close".
     2220. It is also recommended to create a "Release" build. Repeat the steps above from step 3, 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"
    2223
    2324A simulator build is also possible. Another page will be added to provide instructions for that.