Currently, the build directory is placed as a subdirectory in the one where binaries reside.
The problem with this approach is the following. The build directory has the fragments subdirectory with the copied sources.
I need to have my docs directory under which I have the _bin directory with embed-code binaries and the build directory, and on, and on. It looks like this:
It would be good to have a configuration file in the same directory with the binaries that would tell to put working files into the build directory of the module. In my case, docs/build using the configured name, e.g. docs/build/embed-code where fragments would be places.
This also assumes that we already made embed-code smarter to ignore well-known non-source code directories like build, .gradle, etc.
Currently, the
builddirectory is placed as a subdirectory in the one where binaries reside.The problem with this approach is the following. The
builddirectory has thefragmentssubdirectory with the copied sources.I need to have my
docsdirectory under which I have the_bindirectory withembed-codebinaries and thebuilddirectory, and on, and on. It looks like this:It would be good to have a configuration file in the same directory with the binaries that would tell to put working files into the
builddirectory of the module. In my case,docs/buildusing the configured name, e.g.docs/build/embed-codewherefragmentswould be places.This also assumes that we already made
embed-codesmarter to ignore well-known non-source code directories likebuild,.gradle, etc.