It may be necessary to have a different template for each hcc branch,
because building for each branch is sufficiently different that
it is not effective to try to resolve the differences with just a
substitution
The hcc repository can track dependent modules better with a
git clone --recursive strategy rather than using the repo tool. The
repo tool is still used to build ROCm-Device-Libs
Hip is also built inside inside of the container and uses the hcc-lc
build
Cleaning up dockerfiles to remove entrypoints; these containers are
meant to be used more as data containers
Updated readme
Problems getting roct to build with cmake; using deb package for now
:shipit:
* Refactoring after ROCm 1.0 release
ROCm installation paths have changed, and the 1.0 release created a
new installation heirarchy.
* Refactored rocm-project to use amd apt-get packages repo
In the docker-compose yaml file, a new target to launch rocm-project
without mapping any volumes is available. This target only uses the
binary bits availalbe from the amd apt-get repo. The old targets were
merged into a new one, and now map the built from source bits on top
of the amd apt repo data, hiding it.
License changed to MIT
* Adding HSAIL binary blogs to rocr container
Removing WORKPATH from most data-only containers
Reverted hcc-hsail to master branch for --develop based on
failure to build
* Updates to README to describe new 1.0 containers
Removed the setenv scripts which are no longer needed
Refactored 'lib' install path
Changed the names of application targets in .yml file
In the docker-compose yaml file, a new target to launch rocm-project
without mapping any volumes is available. This target only uses the
binary bits availalbe from the amd apt-get repo. The old targets were
merged into a new one, and now map the built from source bits on top
of the amd apt repo data, hiding it.
License changed to MIT
* Changes to the installation directory for roct & rocr
Both projects are adopting a new directory layout convention
* Updating install paths in roct and hcc-isa projects
* Adding docker-compose
Adding docker-compose configuration file to define how containers
should be linked and what data to share.
Adding setenv files to the hcc containers
* New templating engine to generate dockerfiles on disk
Changing roc-setup script to generate dockerfiles, so
images are built with build contexts. Now, roc-setup only
generates dockerfiles, and leverages the docker-compose utility to
build images and compose the shared volumes
* Adding thunk and runtime to docker compose file
Building the thunk and runtime components with docker
compose. Refactoring of various template files.
* Further docker-compose development
Added lots of little features and refactorings
1. Eliminated remove-image and dry-run options from roc-setup as
redundant
2. Templated the install location of volumes
3. Rewrote the README file
4. Fixes to the install procedure for ROCT
* Extracting binary hsa libraries, adding kfd device passthrough
HSAIL generated binaries need libraries available in the ROCR debian
package to properly function.
The docker-compose yaml file now passes /dev/kfd access through to the
container
Various cleanup of docker template files
* docker-compose.yml.template fix
The image names for the example rocm-project services were the
same
hcc-hsail has a new github address
hcc-isa includes new instructions to compile in amdphdrs
roc-setup updated with new command line options for removing images
and dry-runs
Updated main README file to contain new instruction for the tempating
preprocessor. Removed stale README files from all sub-projects.
Fixed roc-setup to execute docker build
The ROC infrastructure has a few permutations that are useful
in different circumstances. Namely, the branch to build source from
and the build configuration. Instead of creating seperate dockerfiles
for each variant, which could explode, the setup script has been
changed into a templating engine, wherin it transforms a docker template
file into a real dockerfile by substituting keywards. It is similar
to a pre-processor for the dockerfiles.
The /dev branch is receiving updates, and it's not sure when the /master
branch will be pushed into. Switching the dockerfiles to use the /dev
branch so that we can test out the latest features.
Dockerfiles have been changed to pull from the develop
branches by default. Release dockerfiles will now clean
up the entire build trees to keep the images as small as
possible.
The new hcc-project dockerfile is meant to be used as a template
to base new ROC application software development on. Removing the
older hcblas dockerfiles as they are no longer relevant.
Added different dockerfiles to build the runtime or to install
from prepackaged ubuntu packages. Refactored a lot of the
dockerfiles, to minimize install size and to install libraries and
configuring their location with ldconfig
