nimforum mirror - Add a JS-backend only option to nim.cfg

halloleo (orginal) [2021-05-06T06:23:10+02:00] view original

I use ~/.config/nim/nim.cfg to adjust the default compiler options.

In there I would like to set the -d:release option, but only when the JS backend was selected.

Is this possible in the nim.cfg file?

DeletedUser (orginal) [2021-05-06T07:14:50+02:00] view original

I believe you have to do:

@if js:
  define:release
@end

With a .nims file:

if defined(js):
  --define:release

This might need when instead of if, but I'm not sure.

Araq (orginal) [2021-05-06T07:30:33+02:00] view original

Because the global nim.cfg contains


@if release or danger:
  stacktrace:off
  excessiveStackTrace:off
  linetrace:off
  debugger:off
  line_dir:off
  opt:speed
  define:release
@end

and is processed before your custom config file, when you set -d:release it's too late and you don't get the release mode.

A very annoying gotcha we're still trying to solve, somehow.

halloleo (orginal) [2021-05-06T10:28:45+02:00] view original

Mmmmh,


@if js:
  define:release
@end

doesn't seem to work for me.

Can I use a .nims file instead of ~/.config/nim/nim.cfg? Is it then called ~/.config/nim/nim.nims?

Yardanico (orginal) [2021-05-06T10:32:11+02:00] view original

Just FYI - you can't put "d:release" in a config file anyway :)

Clonk (orginal) [2021-05-06T11:12:47+02:00] view original

Does config file include both .cfg file and .nims file ?

I use switch("define", "danger") in config.nims and when compiling I get Hint: 210575 lines; 9.281s; 435.492MiB peakmem; Dangerous Release build; which indicates that danger was taken into account.

Is that message not accurate ?

Araq (orginal) [2021-05-06T11:17:42+02:00] view original

Is that message not accurate ?

I wouldn't count on it...

Clonk (orginal) [2021-05-06T11:27:03+02:00] view original

Then which way should be used to store compiler flags ?

There's no build log to verify afterwards and apparently we can neither trust config file or compiler message.

mikra (orginal) [2021-05-06T11:36:08+02:00] view original

you can activate very good build logging: just use " --listCmd --hint:cc --hint:link ". as a ref: https://github.com/nim-lang/Nim/issues/17575

Clonk (orginal) [2021-05-06T11:44:59+02:00] view original

This shows the flag used by the C compiler, not the Nim compiler.

mikra (orginal) [2021-05-06T13:01:08+02:00] view original

well that's right. never thought about that. you could play with "--skipCfg:on|off --skipUserCfg:on|off --skipParentCfg:on|off --skipProjCfg:on|off" and set the flags for your own. But never tried that. Unfortunately "--verbosity:3" doesn't output the current config-set.

halloleo (orginal) [2021-05-07T06:02:21+02:00] view original

I guess, a workaround can be to set the options myself (and overwrite what's set before):


@if js:
  stacktrace:off
  excessiveStackTrace:off
  linetrace:off
  debugger:off
  line_dir:off
@end

Araq (orginal) [2021-05-07T06:15:56+02:00] view original

That's the workaround to use, yes.

halloleo (orginal) [2021-05-07T06:49:51+02:00] view original

Thanks, Araq.

I now tried it. I put


@if js:
  stacktrace:off
  excessiveStackTrace:off
  linetrace:off
  debugger:off
  line_dir:off
@end

in the nim.cfg, but when I run

nim js myfile.nim

myfile.js still contains the debug lines.

A bit of testing showed: The nim.cfg is read, but somehow the @if js: does not get triggered through the JS backend.

Araq (orginal) [2021-05-07T06:56:46+02:00] view original

Hmm well, you don't need the @if at all, do you.

halloleo (orginal) [2021-05-07T07:05:14+02:00] view original

Well, I need the if because I want to switch off debugging only for the JS backend.

Mirror of forum.nim-lang.org

7931 :: Add a JS-backend only option to nim.cfg