Linking a library with an addon

[toly-k]

I am writing an addon that wraps a C++ library. Unfortunately I am having difficulties loading that library with atom-shell.
This is my binding.gyp:

{
    "targets": [{
        "target_name": "addon",
        "sources": ["test.cc"],
        "include_dirs": [
            "Headers",
        ],
        "link_settings": {
            "libraries": [
                "-lmylib.lib",
            ],
            "library_dirs": [
                "Lib",
            ],
        },
    }]
}

It works for tests with node test.js

//test.js
var addon = require('./build/Release/addon');

However when I do the same with atom.exe test.js it throws an exception "The specified module could not be found". Removing dependency on the library fixes the error, so I assume it is looking for mylib.lib in the wrong place?
A lot of the answers I found have an absolute path to a library i.e. /usr/lib
Is it possible to keep the library file locally?

[zcbenz]

Can you try adding .node in the filename? Like require('./build/Release/addon.node');

[toly-k]

@zcbenz I get the same error.

However if I remove dependency on mylib.lib from the binding.gyp and commenting out relevant code from the addon, test.js executes just fine. So I suspect the error signals that atom can't find mylib.lib?

[zcbenz]

Can you check if the build/Release/addon.node exists? It is possible that the build failed when mylib.lib was present.

[anaisbetts]

This message also gets thrown when you rename the EXE (#713) or any other import fails when loading the DLL. Check via depends.exe (http://www.dependencywalker.com/) if all the imports are legit.

[toly-k]

@paulcbetts Thanks, that helped.

[dougludlow]

@paulcbetts thanks for the suggestion to use Dependency Walker. I figured out the module I was importing was missing a .dll: http://stackoverflow.com/questions/41253450/error-the-specified-module-could-not-be-found/