DUB: can I fully control the output file name?

2016-08-09 Thread timepp via Digitalmars-d-learn
I'm writing a Total Commander plugin, which has the "wdx" file extension, so I wish to let dub generate xxx.wdx directly but not xxx.dll. How can I write my file to achieve this goal? --- my dub.json: { "name": "tckeyex", "targetType": "dynamicLibrary", "description": "A minimal

Re: DUB: can I fully control the output file name?

2016-08-09 Thread rikki cattermole via Digitalmars-d-learn
On 09/08/2016 8:49 PM, timepp wrote: I'm writing a Total Commander plugin, which has the "wdx" file extension, so I wish to let dub generate xxx.wdx directly but not xxx.dll. How can I write my file to achieve this goal? --- my dub.json: { "name": "tckeyex", "targetType": "dynamicLib

Re: DUB: can I fully control the output file name?

2016-08-09 Thread lobo via Digitalmars-d-learn
On Tuesday, 9 August 2016 at 08:49:43 UTC, timepp wrote: I'm writing a Total Commander plugin, which has the "wdx" file extension, so I wish to let dub generate xxx.wdx directly but not xxx.dll. How can I write my file to achieve this goal? --- my dub.json: { "name": "tckeyex", "ta

Re: DUB: can I fully control the output file name?

2016-08-09 Thread lobo via Digitalmars-d-learn
On Wednesday, 10 August 2016 at 00:27:44 UTC, lobo wrote: On Tuesday, 9 August 2016 at 08:49:43 UTC, timepp wrote: [...] Have you tried "targetName":"tckeyex.wdx" ? To get a different name for 32/64 bit you may require a configuration for each and run $ dub build -cx86 release $ dub build