Thread overview
How bundles a Dlang application and all its dependencies into a single .exe package?
Dec 01
Marcone
Dec 01
Dennis
December 01
My program have Qt5 GUI that use dlls, icons, pictures, etc.

How bundles a Dlang application and all its dependencies into a single .exe package?
December 01
On Sunday, 1 December 2019 at 20:05:40 UTC, Marcone wrote:
> My program have Qt5 GUI that use dlls, icons, pictures, etc.
>
> How bundles a Dlang application and all its dependencies into a single .exe package?

There are several tools creating installers such as nsis. However, if you want to make an all-in-one portable app (there are tools doing it too), you have to be sure that the licenses of your dependencies allow doing it. I don't think you are allowed to do it using Qt.
December 01
On Sunday, 1 December 2019 at 20:05:40 UTC, Marcone wrote:
> How bundles a Dlang application and all its dependencies into a single .exe package?

You can embed files in the .exe using the import statement:
https://p0nce.github.io/d-idioms/#Embed-a-dynamic-library-in-an-executable
December 01
On Sunday, 1 December 2019 at 20:05:40 UTC, Marcone wrote:
> My program have Qt5 GUI that use dlls, icons, pictures, etc.
>
> How bundles a Dlang application and all its dependencies into a single .exe package?

I've used https://github.com/rikkimax/Bin2D in the past. I've never thought about the license issue before with dlls. probably some kind of grey area here. since they would still be seperate from the executable but also contained in them?
December 02
On 02/12/2019 9:05 AM, Marcone wrote:
> My program have Qt5 GUI that use dlls, icons, pictures, etc.
> 
> How bundles a Dlang application and all its dependencies into a single .exe package?

Placing all your assets into an exe is usually done if the exe itself is self extracting (and doesn't link against a shared library, dynamically is fine). In other words it doesn't have your code linked in.

There is no one right way to do this.
As others have stated e.g. NSIS, Bin2d(mine).

Unless the size of the assets are small-ish, I wouldn't want it all to be stored in the executable that contains your code. It would be too big and have problems.

Keep them separate and have an installer if a zip archive isn't good enough ;)