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

Add curl to .nimble #83

Open
uninhm opened this issue Jul 15, 2020 · 7 comments
Open

Add curl to .nimble #83

uninhm opened this issue Jul 15, 2020 · 7 comments

Comments

@uninhm
Copy link

uninhm commented Jul 15, 2020

/tmp/gintrosalewski/gen.nim(39, 8) Error: cannot open file: gir
stack trace: (most recent call last)
/tmp/nimblecache/nimscriptapi.nim(180, 29)
/tmp/nimble_6719/githubcom_stefansalewskigintro/gintro_6719.nims(81, 7) installBefore
/tmp/nimble_6719/githubcom_stefansalewskigintro/gintro_6719.nims(66, 7) prep
/usr/lib/nim/system/nimscript.nim(260, 7) exec
/usr/lib/nim/system/nimscript.nim(260, 7) Error: unhandled exception: FAILED: nim c gen.nim [OSError]
     Error: Exception raised during nimble script execution

With nimble install gintro on Arch Linux

Info:

nimble v0.11.4
Nim Compiler Version 1.2.0 [Linux: amd64]
Kernel: 5.7.8-arch1-1
@uninhm
Copy link
Author

uninhm commented Jul 15, 2020

Solved installing wget :)

Maybe you should add curl to the .nimble

@uninhm uninhm changed the title Error: cannot open file: gir; FAILED: nim c gen.nim [OSError] Add curl to .nimble Jul 15, 2020
@uninhm
Copy link
Author

uninhm commented Jul 15, 2020

Solved on pr #84

@StefanSalewski
Copy link
Owner

Thanks for reporting.

You are the first and only Arch Linux user who suffers from this issue -- fine that you found a solution for yourself.

We will try to investigate this issue soon in more detail.

@uninhm
Copy link
Author

uninhm commented Jul 15, 2020

Yes, probably most people already have wget installed.

@uninhm
Copy link
Author

uninhm commented Jul 15, 2020

I made a pull request if you want to revise it.

@iNode
Copy link

iNode commented Jul 20, 2020

That's just a tool availability issue.

It won't happen once files from oldgtk3 repository will be available directly in this repository. As a result it won't depend on either curl or wget. See #85.

@StefanSalewski
Copy link
Owner

Yes, maybe I should delete oldgtk3 and simple move the 3 files from oldgtk3 to gintro.

Or maybe strip from these 3 files all what is not necessary for gintro and then copy to gintro, but that is some work.

Another idea would be to do bootstrapping with gintro generated files instead with c2nim generated files. But that seems to be really much work, we would have to generate these 3 files with gintro and then modify the files so that they work for 32 and for 64 bit and for Linux, Mac and Windows at the same time.

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

3 participants