On Monday, 30 July 2018 at 10:23:06 UTC, CC wrote:
With "targetPath", it sounds like I'd need to modify a file
(DUB's .json file) that's in the source tree to indicate where
some(?)/all(?) of the files resulting from the build would be
stored.
Yes.
But it sounds like I'm maybe fighting DUB's
On Monday, 30 July 2018 at 01:50:23 UTC, CC wrote:
[...]
My usual modus operandi is:
1. check out the project into some directory "foo".
2. create another directory "foo.build", somewhere outside of
"foo".
3. "cd foo.build"
4. Run some configuration script/file located in "foo", to
generate "f
On Monday, 30 July 2018 at 07:34:04 UTC, Alex wrote:
I've started playing with "dub", and it *seems* to assume that
you want the files generated during the build process to
reside directly inside your checked-out source tree.
Is that true? And if so, am I fighting dub's design by
attempting
On Monday, 30 July 2018 at 01:50:23 UTC, CC wrote:
Before starting with D programming, most of my projects have
configured their build systems with Autotools or CMake, and git
for source control.
With those systems, it's usually considered best practice to
store all files generated during con
Before starting with D programming, most of my projects have
configured their build systems with Autotools or CMake, and git
for source control.
With those systems, it's usually considered best practice to
store all files generated during configuration and build to be
located outside of the s
