Compiling a project with DQMH cloneable modules not working

[t_zander]

Hello,

I have a problem with a compiled project.

This project contains several DQMH modules that call each other.

The problem: In the clonable modules almost all external VIs are not found, but also some own VIs of these modules are not found.

I have set the included libraries in the Application Builder to "Alway Included".

But if I configure the target directory to a folder, the "missing" files are located in this folder.

I have tried different combinations for the target and the "always include" setting.

When I create a new cloneable module, it executes.

If I compile a cloneable module alone, it does not work, no matter if I set all external libraries to "always included" or not. It even gets worse when I compile it on its own than when I build the whole project (see 3rd image vs 2nd image).

Some of the modules are located directly in this project, others are included from other projects.

It seems that only the clonable modules are causing problems, because singleton modules do not return an error after executing the start module VI, but the clonable modules do.

I have already asked a more experienced colleague, but he doesn't know either.

What information do you need to help me?

Here are two clonable modules with the missing VIs.

Figure 1 is a module and figures 2 to 4 are a module. The last figure shows the BD in development mode.

Thanks and Best, T. Zander

[Ozfarmboy]

You shouldn't need to add the VIs to "Always Included".  

Can you create a simple project with just one DQMH module, and build an exe from the API Tester?

Does this work?

If not, what does the files view show - does it show that all VIs are within one folder (other than Program files) or are there other dependencies.

Also, what does the dependencies look like?

Are you calling VIs from a library that has broken VIs in it?  Or have you got broken VIs inside your project?

[t_zander · Accepted solution]

Ok, thanks for the inspiration :D.

I've pretty much found the answer.

The problem was the settings in the "Additional exclusion".

With this combination it works: