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

Ability to use locally installed zig for supported targets #184

Open
2 tasks done
Jacalz opened this issue Mar 27, 2023 · 4 comments
Open
2 tasks done

Ability to use locally installed zig for supported targets #184

Jacalz opened this issue Mar 27, 2023 · 4 comments
Labels
enhancement New feature or request

Comments

@Jacalz
Copy link
Member

Jacalz commented Mar 27, 2023

Checklist

  • I have searched the issue tracker for open issues that relate to the same feature, before opening a new one.
  • This issue only relates to a single feature. I will open new issues for any other features.

Is your feature request related to a problem?

Downloading docker images can be both be slow and take up storage space. For most devices this is not a huge issue but we might be able to save some of this time and space by using a locally installed version of zig. If we are compiling for a target that do not requite extra libraries and such, we should be able to use a local version of zig if available.

Is it possible to construct a solution with the existing API?

It might be a bit complicated with which targets (os/arch) are possible to compile to without needing the docker containers but should be doable otherwise.

Describe the solution you'd like to see.

If the user has the zig binary in their path, we can add an option to avoid downloading the docker image for some platforms if there is no extra libraries besides Zig are needed for the compile.

@Jacalz Jacalz added the enhancement New feature or request label Mar 27, 2023
@Bluebugs
Copy link
Contributor

It is to be noted that zig is not yet providing a stable release and we had to pick the right version for the right OS so far. It will improve over time, but this might be something to roll only when we are confident that the version of zig we will rely on won't break.

@Jacalz
Copy link
Member Author

Jacalz commented Apr 2, 2023

I think I opened this in the wrong place because I had intended of opening this in fyne-cross but I realized that this kind of makes sense her as well. Should I transfer it or keep it here?

@Bluebugs
Copy link
Contributor

Bluebugs commented Apr 2, 2023

I think there is two things to do. One in fyne cli to adapt cgo parameters when using zig and one in fyne cross to try to pick the local host zig. We could update this one to address the first problem and open another task in fyne cross to cover the second problem.

@andydotxyz
Copy link
Member

I agree there are two - but this sounds very much like what belongs in fyne-cross and we can add a new issue for fyne if desired

@Jacalz Jacalz transferred this issue from fyne-io/fyne Apr 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants