On Friday, 26 February 2021 at 17:57:12 UTC, ryuukk_ wrote:
>     "targetType": "executable",
>
> and it should just run using "dub run"

Unfortunately, the problem remains :/

On Friday, 26 February 2021 at 18:20:38 UTC, Maxim wrote:
> On Friday, 26 February 2021 at 17:57:12 UTC, ryuukk_ wrote:
>>     "targetType": "executable",
>>
>> and it should just run using "dub run"
>
> Unfortunately, the problem remains :/

Looks like something specific to your machine.

The last thing I could think of is to run dub with -v flag (verbose mode), look for all steps performed and check the output for anything that potentially could cause a failure.
Could be related to paths with spaces, path with non-ascii symbols, antivirus software, FS permissions, missing C++ SDK's and runtime libs, compiler toolchain installation, basically anything...

On Fri, Feb 26, 2021 at 06:53:32PM +0000, evilrat via Digitalmars-d-learn wrote:
> On Friday, 26 February 2021 at 18:20:38 UTC, Maxim wrote:
> > On Friday, 26 February 2021 at 17:57:12 UTC, ryuukk_ wrote:
> > >     "targetType": "executable",
> > > 
> > > and it should just run using "dub run"
> > 
> > Unfortunately, the problem remains :/
> 
> Looks like something specific to your machine.
> 
> The last thing I could think of is to run dub with -v flag (verbose mode), look for all steps performed and check the output for anything that potentially could cause a failure.
[...]

And possibly paste the output of -v here, somebody may be able to diagnose what went wrong then.


--T

On Friday, 26 February 2021 at 18:53:32 UTC, evilrat wrote:
> On Friday, 26 February 2021 at 18:20:38 UTC, Maxim wrote:
>> On Friday, 26 February 2021 at 17:57:12 UTC, ryuukk_ wrote:
>>>     "targetType": "executable",
>>>
>>> and it should just run using "dub run"
>>
>> Unfortunately, the problem remains :/
>
> Looks like something specific to your machine.
>
> The last thing I could think of is to run dub with -v flag (verbose mode), look for all steps performed and check the output for anything that potentially could cause a failure.
> Could be related to paths with spaces, path with non-ascii symbols, antivirus software, FS permissions, missing C++ SDK's and runtime libs, compiler toolchain installation, basically anything...

This really might be helpful... I'll try it, thanks!

On Friday, 26 February 2021 at 19:00:57 UTC, H. S. Teoh wrote:
> On Fri, Feb 26, 2021 at 06:53:32PM +0000, evilrat via Digitalmars-d-learn wrote:
>> On Friday, 26 February 2021 at 18:20:38 UTC, Maxim wrote:
>> > On Friday, 26 February 2021 at 17:57:12 UTC, ryuukk_ wrote:
>> > >     "targetType": "executable",
>> > > 
>> > > and it should just run using "dub run"
>> > 
>> > Unfortunately, the problem remains :/
>> 
>> Looks like something specific to your machine.
>> 
>> The last thing I could think of is to run dub with -v flag (verbose mode), look for all steps performed and check the output for anything that potentially could cause a failure.
> [...]
>
> And possibly paste the output of -v here, somebody may be able to diagnose what went wrong then.
>
>
> --T

Sure, I will paste it as soon as I'll have free time.

On Friday, 26 February 2021 at 19:00:57 UTC, H. S. Teoh wrote:
> On Fri, Feb 26, 2021 at 06:53:32PM +0000, evilrat via Digitalmars-d-learn wrote:
>> On Friday, 26 February 2021 at 18:20:38 UTC, Maxim wrote:
>> > On Friday, 26 February 2021 at 17:57:12 UTC, ryuukk_ wrote:
>> > >     "targetType": "executable",
>> > > 
>> > > and it should just run using "dub run"
>> > 
>> > Unfortunately, the problem remains :/
>> 
>> Looks like something specific to your machine.
>> 
>> The last thing I could think of is to run dub with -v flag (verbose mode), look for all steps performed and check the output for anything that potentially could cause a failure.
> [...]
>
> And possibly paste the output of -v here, somebody may be able to diagnose what went wrong then.
>
>
> --T

This is an output:

D:\DEVELOPMENT\[ D ]\sandbox>dub run -v
Using dub registry url 'https://code.dlang.org/'
Refreshing local packages (refresh existing: true)...
Looking for local package map at C:\ProgramData\dub\packages\local-packages.json
Looking for local package map at C:\Users\MAX_PC\AppData\Local\dub\packages\local-packages.json
Try to load local package map at C:\Users\MAX_PC\AppData\Local\dub\packages\local-packages.json
Looking for local package map at D:\DEVELOPMENT\[ D ]\sandbox\.dub\packages\local-packages.json
Note: Failed to determine version of package sandbox at .. Assuming ~master.
Refreshing local packages (refresh existing: false)...
Looking for local package map at C:\ProgramData\dub\packages\local-packages.json
Looking for local package map at C:\Users\MAX_PC\AppData\Local\dub\packages\local-packages.json
Try to load local package map at C:\Users\MAX_PC\AppData\Local\dub\packages\local-packages.json
Looking for local package map at D:\DEVELOPMENT\[ D ]\sandbox\.dub\packages\local-packages.json
Refreshing local packages (refresh existing: false)...
Looking for local package map at C:\ProgramData\dub\packages\local-packages.json
Looking for local package map at C:\Users\MAX_PC\AppData\Local\dub\packages\local-packages.json
Try to load local package map at C:\Users\MAX_PC\AppData\Local\dub\packages\local-packages.json
Looking for local package map at D:\DEVELOPMENT\[ D ]\sandbox\.dub\packages\local-packages.json
Generating using build
Configuration 'application' of package sandbox contains no source files. Please add {"targetType": "none"} to its package description to avoid building it.
Package with target type "none" must have dependencies to build.

On Friday, 26 February 2021 at 18:53:32 UTC, evilrat wrote:
> On Friday, 26 February 2021 at 18:20:38 UTC, Maxim wrote:
>> On Friday, 26 February 2021 at 17:57:12 UTC, ryuukk_ wrote:
>>>     "targetType": "executable",
>>>
>>> and it should just run using "dub run"
>>
>> Unfortunately, the problem remains :/
>
> Looks like something specific to your machine.
>
> The last thing I could think of is to run dub with -v flag (verbose mode), look for all steps performed and check the output for anything that potentially could cause a failure.
> Could be related to paths with spaces, path with non-ascii symbols, antivirus software, FS permissions, missing C++ SDK's and runtime libs, compiler toolchain installation, basically anything...

It works! Thank you so much! The problem was in spaces in the path.