Build A Product from therepo

Prerequisites

  1. Docker installed and correct container type is selected (if on Windows Host OS)

  2. Fuzeapp installed.

  3. workspace.ini file created and located in C:\code (Windows) or ~/code (Linux or MacOS)

  4. Workspace created with therepo

Your workspace file system looks like:

c:\code or ~/code
    - workspace.ini
    - \therepo

Note

The first time you execute Fuze, it must download the Docker container(s). This operation can take a long time depending upon your network connection and the size of the container.

Once downloaded, subsequent executions will not require this step unless Fuze has been updated. If Fuze is updated, only the updates will be downloaded (automatically).

Build release target of a product

$ cd ~/code
$ fuze --build-map therepo/build/mybuildmap.json --target release

Building “all” Targets in a Build map

In the command above, you specified a particular target (release) for building. To build “all” targets defined in the build-map, call the build without specifying a target. For example:

$ fuze --build-map therepo/build/mybuildmap.json

Success Indications

If successful, you will see the following indications in the stdout:

++++++++++++++++++++++++++++++++
[product] build status: SUCCESS
++++++++++++++++++++++++++++++++

...

++++++++++++++++++++++++++++++++
Fuze ID is <FuzeID>
++++++++++++++++++++++++++++++++

Output Location

If successful, you will find the object output of your build in the expected local file system location according to the make. In this case:

<code>/therepo/product/output

You will find the fuze.out file in the workspace dir.

Other Status and Potential Indications

If you use a Windows host OS and do NOT have the proper container type (i.e., Windows or Linux) selected in Docker, you will see the following type of indicator in stdout:

Checking if switching to Windows containers is necessary...
You are currently running Windows containers; please switch to Linux containers now

You will see the following type of stdout trace while the Fuze container is being downloaded:

54ee1f796a1e: Pull complete
f7bfea53ad12: Pull complete
46d371e02073: Pull complete
b66c17bbf772: Pull complete
73caaaf3db60: Pull complete
3c8db65c39f9: Pull complete
3db52b4593f7: Pull complete
...