Open
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
With this commit I have made some changes which should improve GtkD usage experience.
First of all I want to say that compiletime link of gtk and other G-type libraries is useless. On unix based machines we always have dynamic libraries(or can download it via our packet manager) and so don't need static linkage in general. If we talk about Windows computers - it is a bit more easier to download .dll files from MSYS or like this than compile it yourself. GTK applications becomes more popular, it means that using of dynamic libraries is better because this way uses less memory: (some shared libraries)*1 < (some apps with staticly linked libraries)*n. I made some changes because think that it is truth.
Additional info: because gtkd.Loader was replaced by linker.Loader there are some changes in gir-to-d. I forked it and replaced wrap/ link with my repo