-
Notifications
You must be signed in to change notification settings - Fork 41
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
Error when making NRO on Linux #18
Comments
does this occur on the previous version? Ive changed the working directories away from the root, i have a feeling this may have caused some issues on other platforms? |
Will check right now |
In which build did you start the conversion? |
3.3.4 is the change, 3.3.2 or even 3.3.3 should be untouched. |
Building seems to work on 3.3.2, but I can't fully test it out due to the timeout timer. Is there a way to overwrite the timer to give me more building time? |
Nevermind, I seem to be having issues with my keys, will report back in a moment |
Sounds good! |
Keys issue fixed. However, I'm still being timed out, but I do make it all the way to the Summary. I just don't get a result NSP |
Was looking in wrong directory. Will test with one of the resulting NSPs in the folder I just found |
Issue is pretty much resolved. Just put a note in the wiki that Linux users should use ver. 3.3.2 and that the error it outputs is false if their terminal outputs a Summary, and that the NSP can be found in /Nro2Nsp/temp |
ill try and look into that issue and fix it in the current versions, the output nsp should be int the nro2nsp.exe directory normally |
It outputs to the top most level of the file system. which is a huge no no |
It looks like it works if you run it in wine; I think it uses windows-specific APIs that doesn't work under plain mono that gets implemented by wine. |
On Linux, I run into the issue where the hacbrewpack reports an error, stating that it can't find certain directories, leading to a --hacbrewpack error. This is what my terminal spits out when it encounters the issue:
The text was updated successfully, but these errors were encountered: