Skip to content

Conversation

oblitum
Copy link
Contributor

@oblitum oblitum commented Sep 28, 2013

Improves the installation instructions of the "everywhere else" section
describing usage for Qt compiled from latest repository sources.

Improves the installation instructions of the "everywhere else" section
describing usage for Qt compiled from latest repository sources.
@niemeyer
Copy link
Contributor

Thanks, but I'm afraid these instructions are not for "everywhere else". It's one more example that works in specific circumstances. If you'd like to add instructions that work in a real environment not yet listed, that'd be welcome, but otherwise we already have examples right above that last note that can be used as guidelines.

@niemeyer niemeyer closed this Sep 30, 2013
@oblitum
Copy link
Contributor Author

oblitum commented Sep 30, 2013

Ok. I think these are good general *nix guidelines for using from sources that I missed, the others are package and/or system specific and somewhat not clear how to map. I myself, as I have everything from repo, started by go get, got errors and figured out from them what I needed to do.

@niemeyer
Copy link
Contributor

Ok, but what's your environment? We can have instructions for it as well. It's better to have realistic instructions that are known to work on a given environment than to provide wildcard ones that will fail in some cases (MacOS is a *nix, and these instructions do not work there, for example).

@oblitum
Copy link
Contributor Author

oblitum commented Sep 30, 2013

my environment is ubuntu using qt compiled with clang from sources, and go too compiled from repository sources. I think the same would apply for OS X too, if one is using stuff from repository sources (as I used to do on OS X).

@oblitum
Copy link
Contributor Author

oblitum commented Sep 30, 2013

The Windows setup is the simple one by providing raw path configurations, the others are a bit cluttered with package manager information and there's no simple notice about setting PKG_CONFIG_PATH and CGO_CPPFLAGS paths for *nix usage in general, which I think may be helpful.

@oblitum oblitum deleted the improve-everywhere-else-usage-description branch December 29, 2013 01:40
ricochet1k referenced this pull request in limetext/qml-go Aug 19, 2016
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

Successfully merging this pull request may close these issues.

2 participants