In order to create a "bundle" installer that installs the application build output from multiple projects I have a project with the build folders from those other projects included as auto-populated folder. This works fine, but one of the builds now have an external .llb file included, and the final installer ends up adding that file not as just an .llb file in its original folder (where the application build correctly puts it), but as an .llb file within a regular folder named the same as the llb file.
So let's say that one of the applications have a file named PlugInA.llb in a folder named PlugIns. Then the installer ends up putting that file into an extra folder, so that the path becomes PlugIns\PlugInA.llb\PlugInA.llb.
Is there a way to avoid this? I do not want a solution that involves conversion to an lvlib-file for example, or having one installer that just runs multiple separate installers...(both of these might work around the issue yes, but they have other effects as well that I do not wish). The installer should just treat the llb file as a flat file that is to be included as it is.
