You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having added dependency build automation to HammerDB in PRs #323#362 means that the current installation format of HammerDB with source included is no longer required. In particular, adding Docker support means a more streamlined binary format would be preferable, e.g. the Docker format supports CLI only however the installation includes all HammerDB files.
A logical next step is to enhance the build automation to produce standalone executables for Windows and Linux.
The current source release would still be produced by the build automation, the standalone executables would be an additional step.
There are multiple approaches to building these such as TclKit and Freewrap. This issue covers evaluating whether such an approach is possible/practical and can be incorporated into the build automation process.
The text was updated successfully, but these errors were encountered:
Further research shows that zipkit functionality will be included in Tcl 8.7 https://www.magicsplat.com/blog/tcl87-zipfs2/ suggesting that TclKit/ZipKit should be the first approach to evaluate.
Having added dependency build automation to HammerDB in PRs #323 #362 means that the current installation format of HammerDB with source included is no longer required. In particular, adding Docker support means a more streamlined binary format would be preferable, e.g. the Docker format supports CLI only however the installation includes all HammerDB files.
A logical next step is to enhance the build automation to produce standalone executables for Windows and Linux.
The current source release would still be produced by the build automation, the standalone executables would be an additional step.
There are multiple approaches to building these such as TclKit and Freewrap. This issue covers evaluating whether such an approach is possible/practical and can be incorporated into the build automation process.
The text was updated successfully, but these errors were encountered: