I've read the documentation about DUB's config (I'm using the SDL format) and it seems that DUB completely ignores my config. My config file is:

name "test"
description "Testing dub"
authors "rempas"
copyright "Copyright © 2021, rempas"
license "AGPL-3.0"
compiler "ldc2"

configuration "development" {
  platforms "linux"
  build "dubug"
  compiler "ldc2"
  targetType "executable"
}

configuration "release" {
  platforms "linux"
  dflags "-Oz" platform="/bin/ldc2"
  build "release"
  compiler "ldc2"
  targetType "executable"
}

I'm compiling using dub --config=development and I'm getting the following line: Performing "debug" build using /usr/bin/dmd for x86_64. The same exactly happens when I'm trying to do the release config. If I disable the targetType option, it seems that it's creating a library and I can also manually change the compiler and the build-type so I don't know what's going on....

On Saturday, 22 May 2021 at 20:28:56 UTC, rempas wrote:

name "test"
description "Testing dub"
authors "rempas"
copyright "Copyright © 2021, rempas"
license "AGPL-3.0"
compiler "ldc2"

configuration "development" {
  platforms "linux"
  build "dubug"
  compiler "ldc2"
  targetType "executable"
}

configuration "release" {
  platforms "linux"
  dflags "-Oz" platform="/bin/ldc2"
  build "release"
  compiler "ldc2"
  targetType "executable"
}

Ignoring the "dubug" typo...normally, I think you pass compiler values directly to dub via the --compiler flag. For example:

dub --config=development --compiler=ldc2

Note: you can also pass "debug" and "release" builds (among others), like so:

dub -b "debug" --compiler=ldc2

Passing in the compiler allows any end user building your code to use whatever compiler they want. Otherwise, something like toolchainRequirements dmd="no" ldc=">=1.21.0" may achieve what you want.

Thanks,

Jordan

On Saturday, 22 May 2021 at 20:28:56 UTC, rempas wrote:

I just looked in the dub documentation for "build" and "compiler" entries, which I had never heard of, and I see none now. As Jordan said, those have always been configured on the command line. Did you perhaps see something about those somewhere else?

FYI, the first configuration you define is always the default, so you don't need to specify it on the command line unless you really want to.

On Sunday, 23 May 2021 at 00:36:48 UTC, Jordan Wilson wrote:

dub --config=development --compiler=ldc2

dub -b "debug" --compiler=ldc2

Hi, and thanks a lot for your time. Yes I fixed the typo. Passing values directly works like I said but I'm wondering why choosing a config won't effect things like the compiler or the build type. Anyway, have a nice day my friend!

On Sunday, 23 May 2021 at 04:56:18 UTC, Mike Parker wrote:

I've saw the SDL format config documentation here. Maybe I'm wrong idk...

On Saturday, 22 May 2021 at 20:28:56 UTC, rempas wrote:

Hello,

DUB has two separate concepts:

- buildTypes: default ones are debug, release, release-debug, release-nobounds
  They
  You can define custom buildTypes.
  Selected with -b
  https://dub.pm/package-format-json.html#build-types
  By default, "debug" build type.


- configurations are more often used to define software options
  You can define custom configurations.
  Selected with -c
  By default the first one in your file is taken, else it's a default configuration.

People use configurations to define example programs or platform builds (probably becase buildTypes are limited), but they are primarily intended for enabling or disabling features in software.

On Sunday, 23 May 2021 at 09:45:06 UTC, Guillaume Piolat wrote:

Thanks a lot man!