mdBook Assets - Generated Makefile Approach #3847
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
BilalM04
changed the title
|
Closing in favor of #3848. |
|
Do you still need the branch @BilalM04 ? |
|
@balacij I got cut short on time today, I’ll be doing a cleanup of the mdBook stuff tomorrow morning. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Prototype from the discussion in #3835 (comment).
Leverages features proposed by #3841. Each example generates a makefile with the following targets:
build: builds the mdBook project viamdbook buildserver: launches the server of the mdBook project viamdbook serve --openassets: dependency to bothbuildandserver. Copies over the assets into thesrcdirectory.The main
Makefileuses the generated makefiles to build and launch the server of the Drasil examples.