Rupinderjit Singh authored Feb 28, 2023 and Vishnu Banavath committed Apr 20, 2023

it includes:
 * cleanup while integration of unification changes
 * cloning android device profile in envsetup.sh to
   make XML independent of device profile
 * sync mali DDK only if user has access to the source by
   exporting license and source path information
 * updated README.md

Signed-off-by: Rupinderjit Singh <rupinderjit.singh@arm.com>
Change-Id: I01d7ac65fd08946fa7fa5cc56c7dfff82056894d

1)Moved configs from run_docker.sh to common.config
2)Logic to mount the model directory built into run_docker.sh
3)Updated README
4)Included logs for docker image build failure and pull failure

Signed-off-by: Annam Sai Manisha <annam.saimanisha@arm.com>

Changes are such that on executing setup.sh docker image is pulled from container registry and if fails it builds a local image
Readme is updated with steps on how to login to registry(one time process)

Change-Id: Iaf6d6539bf6adca86c750ccfd26cb874cd32cf9d
Signed-off-by: Annam Sai Manisha <annam.saimanisha@arm.com>

Change-Id: Iddefd9734254ab4fa63b13184cedc409b5a277aa
Signed-off-by: Annam Sai Manisha <annam.saimanisha@arm.com>

FVP model can be launched by executing ./run_docker.sh run_model -m model_path_in_container -d distro_opts
Change-Id: Ib86c7768afe5df328cdff42e24df23ea8f9e2969
Signed-off-by: Annam Sai Manisha <annam.saimanisha@arm.com>

Signed-off-by: Tintu Thomas <tintu.thomas@arm.com>
Change-Id: I6ae7663721d3c3024297b4ebc67b709eda64ab39

The change in setup.sh includes:
 * setup the environment to build TC images
 * setup.sh now also builds a Docker image
 * README.md update for the usage

Signed-off-by: Rupinderjit Singh <rupinderjit.singh@arm.com>
Change-Id: I8ef3ed20d56e94c9cc9b1d71c36e14f36415260c

This change supports mte, bti and pauth tests. All the tests
can be run at once using run_kselftest.sh

README.md has been updated with usage informaiton

Signed-off-by: Rupinderjit Singh <rupinderjit.singh@arm.com>
Change-Id: Id1f6bdaeaa25d9d39e5cfcf74df59159e71149d1

Added Dockerfile and other scripts required for building docker image and launching docker container to build TC

Change-Id: Id1e68562fe64ba7e172de264a62e674ff05dbd6e
Signed-off-by: Annam Sai Manisha <annam.saimanisha@arm.com>

1.Added a requisites file
2.Changes are such that whenever the  components code is changed and built then its dependencies are also built

Change-Id: I17289197fe0b990064203d33aa47224a90bd9481
Signed-off-by: Annam Sai Manisha <annam.saimanisha@arm.com>

Signed-off-by: Salome Thirot <salome.thirot@arm.com>
Change-Id: I0c3a57723f3897e797c25194024c418289507fb4

As build-scripts scales up to support platforms specfic tests, there is
a need to create a platform specific directory to hold the platform
specfic test build scripts. One of the ways to organize the platform
specfic test build scripts could be as below

	build-scripts
		|
		|-- build-<component1>.sh
		|-- build-<component2>.sh
		|-- .
		|-- .
		|-- build-<componentX>.sh
		|-- build-test-TEST1.sh
		|-- build-test-TEST2.sh
		|-- .
		|-- .
		|-- build-test-TESTX.sh
		|
		|-- configs
		|	|
		|	|-- <platform1>
		|	|-- <platform2>
		|	|-- .
		|	|-- .
		|	|-- <platformX>
		|
		|-- <platform1>
		|	|
		|	|-- <build-test-TEST1>.sh
		|	|-- <build-test-TEST2>.sh
		|	|-- .
		|	|-- .
		|	|-- <build-test-TESTX>.sh
		|
		|-- <platform2>
		|	|
		|	|-- <build-test-TEST1>.sh
		|	|-- <build-test-TEST2>.sh
		|	|-- .
		|	|-- .
		|	|-- <build-test-TESTX>.sh
		|
		|-- <platformX>
			|
			|-- <build-test-TEST1>.sh
			|-- <build-test-TEST2>.sh
			|-- .
			|-- .
			|-- <build-test-TESTX>.sh

The existing 'platforms' directory is in fact a bunch of build config
files. So the 'platforms' directory can be renamed as 'configs'
directory to allow adding platform specific directory under the root
of build-scripts directory. This would help to avoid any possible
incorrect interpretation of the purpose of the configs directory
and the platform specific test build scripts directory.

Change-Id: I3ca0576cfdbc7be88d2812fcda841c19c95ce8ca
Signed-off-by: Thomas Abraham <thomas.abraham@arm.com>

If there is only one filesystem/flavour then the -f and -t options
become optional, and omitting them will be the same as specifying the
only available filesystem/flavour with those flags. Also changing so
that if there is only one platform/filesystem/flavour, then
"./build-$COMP.sh $CMD" will work with no options (where $COMP is a
component, or 'all' and $CMD is clean/build/package).

Splitting the public 'platform' into the real platforms. The folder
platforms/public no longer exists and in it's place, there are separate
juno, tc2 and fvp.

Changing the output directory to be "output/platform" for platforms with
only one flavour and "output/platform/flavour" for platforms with
multiple flavours.

Previously, there was a huge amount of find commands to handle
platform/filesystem/flavour detection over these 3 files. They all
needed to be modified to ignore hidden objects, so it was a good time to
ensure that they were abstracted.

Change-Id: Id6054966651d39251665a960047217466c06fb88
Signed-off-by: Dean Birch <dean.birch@arm.com>

Merge the latest build script from ARM's internal repository.

Taken at this SHA ID:
  035649e618f1471413e220ec558a8360b4769d71

  035649e  2016-05-27  build-script refactor      [Sudipto Paul]

This patch squashes down the change history from the series on the
internal tree to this single revision.

Change-Id: I70352fd520aa5206379bb417c6d7e93935b9f101
Signed-off-by: Ryan Harkin <ryan.harkin@linaro.org>