Add .dmd file support to todmp for selective module packaging (CMake only) #179
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The todmp tool now accepts
.dmd(DMOD Dependencies) files to specify which modules to include in a DMP package, instead of packaging all modules in a directory.Changes
Core functionality:
.dmdfiles using existingdmod_dependencieslibrary.dmdas main module (overridable via CLI parameter)#ifdef DMOD_ENABLE_DMD_SUPPORTBuild system:
dmod_dependencieslibrary and definesDMOD_ENABLE_DMD_SUPPORTdmod_dependencieslibrary for future useImplementation details:
mkdtemp()for secure temp directory creation.and..entriesDocumentation:
.dmdusage examples and workflow integrationUsage
With CMake build (includes .dmd support):
With Make build (directory-based only):
# Packages all modules in directory todmp myapp ./modules ./myapp.dmpModules must already be downloaded in the input directory - version specifiers in
.dmdare ignored during packaging.Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.