Generating DEB and RPM files with the source from the rocm-examples.

[Mustaballer]

Adds a script to automate the packaging of ROCm SDK examples into DEB and RPM packages. The script performs the following tasks:

• Sets up necessary package metadata and directories.
• Copies source files and directories to the build directory.
• Creates DEB and RPM packages with the specified metadata and source files.
• Cleans up previous build artifacts to ensure a fresh build environment.

[Mustaballer]

@dgaliffiAMD I tested the deb file generated from my build_packages.sh , and it doesn't include the binary files that show up when I build with the CMakeLists.txt. You can view the contents of the deb file..

There are some issues with the rpm file generation in my script, so I will continue working on fixing those issues.

[Mustaballer]

The rpm file generation also seems to be working, you can view file contents of the rpm file generated from build_packages.sh here
rpm-file-contents.txt

[Mustaballer]

@dgaliffiAMD PR is ready for review! :)

[Beanavil]

Also, this is probably out of the scope of this PR, but AFAIK a GitHub action could be set up to build the packages and add them to the "Releases" section of the repo when, for instance, a release tagged branch rocm-x.y.z is pushed:

# Release workflow file
on:
  push:
    tags:
      - 'rocm-*'

jobs:
  package:
    steps:
      - name: Build packages
        run: Scripts/Package/build_packages.sh

      - name: Release packages
        uses: softprops/action-gh-release@v1
        with:
          draft: true
          files: /path/to/generated/packages

[dgaliffiAMD]

I'm not seeing the install prefix on the generated DEB file anymore. Everything is being installed directly to /. I'm not sure when this started.
Maybe it will help to incorporate the install prefix to you copy_source, when you are setting up the "staging area".