Generate Rules.mk files using Source Orbit does not select CL pseudo-source

[djurrep]

Not sure if this is the right place to ask.
Probably more of an Source Orbit question.

Using BOB with Source Orbit in my project, saves me quite some time when adding, renaming source files.
With a click of a button, I can re-generate the Rules.mk files.
Great stuff!

All (real) source code files are recognized and written to the Rules.mk files for the directory they reside in.
The parent Rules.mk files get the directory name added to the SUBDIRS = line.

This is not the case for CL pseudo-source files.

In my project, service programs and their modules are organized in parallel directories.
e.g.
../Client/Modules
../Client/ServicePrograms
The ../Client/Modules directory contains .SQLRPGLE source files to create the modules.
These are picked up nicely and placed in a Rules.mk file for the same directory. The parent Rules.mk get the directory name added to the SUBDIRS = line.

The ../Client/ServicePrograms directory (only) contains .ILESRVPGM source files, with a CRTSRVPGM command.
These CL pseudo sources are NOT picked up i.e. written to a Rules.mk file for the same directory.
This is not too much of an issue because a 1 generic line in the Rules.mk file will handle this (%.srvpgm: %.ILESRVPGM).

However, as these pseudo sources are not picked up by Source Orbit, their directory name is also not written to the parent Rules.mk file in SUBDIRS = line. Of course that results in the fact BOB cannot find rules to build the service programs (by executing the commands).

Q: Is there a way to get the CL pseudo sources be recognized/processed when generating the Rules.mk files?