The default ib_profile.xml file that is located in the provided by IncrediBuild Linux is located at IncrediBuild installation folder at the following path:
/opt/incredibuild/data/ib_profile.xml

This is the default configuration file that default ib_profile.xml file is used in every build execution as the default configuration file. This instance of the ib_profile.xml file is a “readread-only” only file, and should not be modified, since . If you make any changes in this default file, during an upgrade of IncrediBuild Linux, this file the original default file is restored, and your changes will be overwrittenoverridden.

If you wish want to edit the default ib_profile.xml file, you will need to create a copy of the file, make your changes in the copied file, and save it in one of the following locations:

• Project directory ($PWD/ib_profile.xml) - This file is in the working directory of the project being built. It will only An xml file saved in this location will be used only when running a build from this directory.
• Home directory ($HOME/.ib/ib_profile.xml) - This file is in the home directory of the user. It An xml file saved in this location will be used by every build that is run by the user.
• Machine directory (/etc/default/ib_profile.xml) - This file  - local machine directory. An xml file saved in this location will be used in every build that is running on this machine.

If there are multiple instances of the ib_profile configuration .xml file that include different configurations, IncrediBuild Linux will use the configuration of the most specific location. For example, it IncrediBuild Linux will give preference precedence to the configuration of the project directory over the ones in the home or machine directories. 

Custom Profile Configuration

To edit the profile configuration file:

1. Locate the default profile configuration file - /opt/incredibuild/data/ib_profile.xml.
2. Copy the file and paste it on one or more of the locations described above (e.g. project directory, home directory, etc…).
3. Add the names of the tasks/processes that should be handled locally only (local_only), distributed remotely (allow_remote) and intercepted (Intercepted) followed by the relevant attribute.

Examples

Local only example:
<processes>
<process filename="mylinker"           type="local_only" />
</processes>

Allow remote example:
<processes>
<process filename="mycompiler"           type="allow_remote" />
</processes>

Custom Build Executions

IncrediBuild for Linux Guide: