Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't build 0.10.2 for linux64 on OS X (EISDIR error) #57

Closed
nDmitry opened this issue Aug 16, 2014 · 6 comments
Closed

Can't build 0.10.2 for linux64 on OS X (EISDIR error) #57

nDmitry opened this issue Aug 16, 2014 · 6 comments

Comments

@nDmitry
Copy link
Contributor

nDmitry commented Aug 16, 2014

Get this EISDIR error when trying to build my app for linux64:

It only happens with v0.10.2 (0.10.1 worked fine) and if linux is included in the platforms array. Here's options I pass (except version, they didn't change since 0.10.1):

nodewebkit: {
    dist: {
        options: {
            version: '0.10.2',
            platforms: ['win', 'osx', 'linux32', 'linux64'],
            appName: 'App',
            appVersion: '<%= pkg.version %>',
            distDir: 'build/',
            cacheDir: 'build/cache/',
            macCredits: 'support/Credits.html',
            macIcns: 'support/app.icns'
        },
        src: ['<%= distDir %>/**']
    }
}
@yeco
Copy link

yeco commented Aug 17, 2014

I'm having a similar issue, but setting increasing my ulimit seems to help:

ulimit -S -n 2048

@nDmitry
Copy link
Contributor Author

nDmitry commented Aug 17, 2014

@yeco this doesn't work for me.

@alexeimoisseev
Copy link

Same sh*t :(
ulimit changes don't help

@nDmitry
Copy link
Contributor Author

nDmitry commented Aug 19, 2014

You can download node-webkit versions you need and put them into corresponding cache folders manually.

@gabepaez
Copy link
Contributor

It looks like the tar files are now being distributed with a top level directory like the zip archives. This should be a pretty easy fix. @nDmitry is right that you can just manually correct the cache folders structure as a temporary workaround.

@1j01
Copy link
Contributor

1j01 commented Aug 20, 2014

Would changing this line from header.name = (filename[1] ? filename[1] : filename[0]); to header.name = (filename[2] ? filename[2] : (filename[1] ? filename[1] : filename[0])); fix the issue (in a silly manner)?
It seems to just dump everything into one folder... Is that what is wanted? Maybe header.name = filename[filename.length - 1]; would do better.
The more practical solution of course would be to move the unfolding out of extractZip and have it apply also to extractTar.

1j01 pushed a commit to 1j01/node-webkit-builder that referenced this issue Aug 20, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants