Fix #1538, add capability to generate multiple tables

[jphickey]

Adds a "install_custom.cmake" hook that can be put into a CPU-specific subdirectory under the "defs" directory, that can perform extra installation steps as required for the project/mission.

Tweaks the "add_cfe_tables" function such that it can also be called from the install_custom.cmake script to generate additional/alternative table binary files for that CPU.

The main update is that it uses the "APP_NAME" parameter to associate the table files with the app library, so the same set of include files can be used. This relies on the target-scope properties being used. Historically that string wasn't verified, it could have been any unique string, but now it should match the app if this is to work as expected.

Describe the contribution
Fixes #1538

Testing performed
Add multiple/alternative table definitions for sample_app in a local 2-cpu configuration. Confirm that all table files are built and installed to the staging area correctly, and that sample_app can be tweaked to load one of the alternatives, just by changing the filename it loads.

Expected behavior changes
Because the "APP_NAME" (1st parameter) of add_cfe_tables was never validated historically, it just had to be unique, this still allows any string for backward compatibility. It will generate a new "Note" message to the user if it does not match an application name, but it is still accepted.

If the multiple table feature is used, it actually needs to match the application name, or else the include paths may be incomplete.

System(s) tested on
Ubuntu

Additional context
See also nasa/sample_app#148

Contributor Info - All information REQUIRED for consideration of pull request
Joseph Hickey, Vantage Systems, Inc.

[skliper]

Ping @excaliburtb, does this meet your need for building multiple versions of tables?

[excaliburtb]

This looks like what I would want. Is there a way to add include paths to a specific table?

[jphickey]

This looks like what I would want. Is there a way to add include paths to a specific table?

You can always call the target_compile_definitions and/or target_include_directories cmake commands to configure how these table sources get compiled. This does require you to know the actual target name, which in this case is a combination of the target name, app name, and table basename (i.e. without extension). That is, you can do:

target_include_directories(${TGT}_${APP_NAME}_${TBLWE} ${extra_includes})

[astrogeco]

CCB:2021-05-19 APPROVED

• Lets users install arbitrary files by calling "add cfe tbl"
• Renamed library name to include the TGT_NAME and APP_NAME. Previously it could be an arbitrary string, it is still acceptable but it might result in a build failure.
  • There's an open issue in sample_app <https://github.c<om/First parameter to add_cfe_tables should be app name sample_app#148> to make it compatible with this pattern
• Do we want to add a sample implementation?
  • open issue
• Opened a ticket on elf2cfetbl to enforce naming Should error if output name does not match input name elf2cfetbl#79