On Saturday, 4 March 2023 at 21:31:09 UTC, Richard (Rikki) Andrew
Cattermole wrote:
Yes dub was setup to cover the most common cases, but ignores
when you have multiple outputs. Not ideal.
There is a PR to add build steps currently, which will help
improve things, so there is work to make dub
Yes dub was setup to cover the most common cases, but ignores when you
have multiple outputs. Not ideal.
There is a PR to add build steps currently, which will help improve
things, so there is work to make dub better at these less common use cases.
The simplest solution is to do one package p
On Saturday, 4 March 2023 at 20:23:29 UTC, Steven Schveighoffer
wrote:
On 3/4/23 1:33 PM, Chris Piker wrote:
If you mean that you have multiple subprojects inside your main
dub project, my advice is to follow what other such projects
do. I always look at vibe for my example.
I have been tryi
On 3/4/23 1:33 PM, Chris Piker wrote:
Hi D
I normally work in a *nix environment, typically on server-side code.
For many projects I have gnu makefiles that build a small lib along with
command line utilities.
Up to now I've been creating a dub.json file for just the sourceLibrary,
and the
Hi D
I normally work in a *nix environment, typically on server-side
code. For many projects I have gnu makefiles that build a small
lib along with command line utilities.
Up to now I've been creating a dub.json file for just the
sourceLibrary, and then putting embedded dub comments at the
