# Generate IBM i Build Rules

Analyze IBM i objects and generate codermake build rules

1
Connect
2
Select Objects
3
Analyze
4
Review & Generate

### Connect to IBM i

Host Host name or IP address of the IBM i system to connect to over SSH.
User IBM i user profile used to sign in and run the object analysis.
Password Password for the IBM i user profile. Used to open the connection and not saved in your browser.
Advanced Options
objx Tool Library Library where the objx analysis tool will be installed.

### Select Objects to Analyze

0 objects selected
Branch:
Git branch in the target repository that existing Rules.mk files are merged from and that the resulting build rules task runs on.
Loading libraries...

#### Save Selection

Selection Name Name to save the current object selection under, so you can reload it later from Load Selection.

#### Load Selection

Loading saved selections...

#### Library List

Use library list from JOBD When checked, analysis uses the library list from your user profile's job description (JOBD). Uncheck it to define a custom, ordered library list below.
Type an IBM i library name and click Add to append it to the custom library list. Libraries are searched in the order listed.

#### Options

Require sources for files When checked, physical files and tables must have source to be included. When unchecked, sourceless file dependencies are dropped so they do not block the objects that use them. Allow missing file dependencies When checked, a referenced file that cannot be found is reported as a warning instead of a blocking error, so the dependent object still builds. Search for object sources When checked, the analyzer searches for each object's source rather than relying only on the source location recorded with the object. Generate rules for cross-library dependencies When checked, build rules are also generated for dependencies that live in other libraries. When unchecked, only same-library dependencies and objects you selected get rules.
Replace existing Rules.mk content
When unchecked, new rules are merged into existing Rules.mk files: rules for matching targets are replaced and unrelated existing rules are preserved.

##### Source Type Mappings

Built-in mappings

Type | Extension |
--- | --- | ---

###### Custom mappings

Type | Extension |
--- | --- | ---

No custom mappings defined.
Map an IBM i source member type (for example RPGLE or CLP) to the file extension used for its source in the generated build rules.

### Analyzing Objects

0 / 0

### Review & Generate Rules

Errors (0)
Warnings (0)
Skipped (0)
Target Repository

## Git Connection Required

Authorize the Git providers listed below before CoderFlow can commit the generated build rules to your repository.

This import requires authorization for the following Git providers: