Cant run icarurs verilog code on atom


#1

[Enter steps to reproduce:]

The following is the error I have faced
Atom: 1.34.0 x64
Electron: 2.0.16
OS: Microsoft Windows 10 Home Single Language
Thrown From: gpp-compiler package 3.0.7

Stack Trace

Uncaught TypeError: “file” argument must be a non-empty string

At child_process.js:395

TypeError: "file" argument must be a non-empty string
    at normalizeSpawnArguments (child_process.js:395:11)
    at Object.exports.spawn (child_process.js:508:38)
    at compile (/packages/gpp-compiler/index.js:274:31)
    at compileFile (/packages/gpp-compiler/index.js:216:5)
    at /packages/gpp-compiler/index.js:27:11)
    at CommandRegistry.handleCommandEvent (~/AppData/Local/atom/app-1.34.0/resources/app/static/<embedded>:11:350017)
    at CommandRegistry.dispatch (~/AppData/Local/atom/app-1.34.0/resources/app/static/<embedded>:11:348492)
    at AtomEnvironment.dispatchContextMenuCommand (~/AppData/Local/atom/app-1.34.0/resources/app/static/<embedded>:1:671099)
    at EventEmitter.t (~/AppData/Local/atom/app-1.34.0/resources/app/static/<embedded>:1:678566)
    at emitThree (events.js:136:13)
    at EventEmitter.emit (events.js:217:7)

Commands

     -8:13.2.0 gpp-compiler:compile (div.line)
     -3:57.5.0 platformio-ide-terminal:paste (textarea.)
     -3:46.2.0 core:paste (input.hidden-input)
     -3:45.2.0 core:confirm (input.hidden-input)
     -3:28.4.0 settings-view:check-for-package-updates (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)
     -3:04.6.0 platformio-ide-terminal:paste (textarea.)
     -2:51.8.0 gpp-compiler:compile (div.line)
     -0:26.7.0 gpp-compiler:gdb (div.line)

Non-Core Packages

atom-python-run 0.9.7 
busy-signal 2.0.0 
git-plus 8.6.1 
gpp-compiler 3.0.7 
Hydrogen 2.7.0 
intentions 1.1.5 
language-verilog 0.4.0 
linter-verilog 0.7.0 
platformio-ide-terminal 2.9.0 
script 3.18.1 
verilator-4.010 undefined 
verilog-tools 0.1.0 

#2

Mind posting a screenshot of Atom with the error and your code file visible?

The people on this forum aren’t necessarily going to be able to debug issues for a package that’s been abandoned for three years. It’s possible that it has just broken and you need to use something else to run your code.