-
Notifications
You must be signed in to change notification settings - Fork 77
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
how to run exe's / examples #14
Comments
@sboosali $ nix-shell release.nix -A grpc-haskell.env
$ # Lots of build activity...
[nix-shell:]$ echo-server --help
Runs the echo service
Usage: echo-server [--bind TEXT] [--port INT]
Available options:
-h,--help Show this help text
--bind TEXT grpc endpoint hostname (default "localhost")
--port INT grpc endpoint port (default 50051) @sboosali what is in the |
I did have trouble running |
Yeah, I would recommend the |
i tried
i'll try cabal, thanks for the link! |
Boy that's weird. I get a no compiler found error and when I try to run stack setup I get another very arcane error (all from within the nix-shell environment) but I think following @Gabriel439's advice of using cabal makes sense to me. What is strange though is that |
i tried cabal but got:
these options btw, what version of clang works for you? mine seems to be it builds with the default gcc:
but the exe's themselves seems to work:
either way, i'll read through the tutorial you linked. |
yeah, it's the same as the readme (unless i have a typo?)
|
and i'm pretty sure i'm on the latest version:
|
btw, one issue was that the examples are disabled by default. but then when built with |
Is there any way to use this library without using Nix? Are there plans to remove that dependency later on in the roadmap? Just wondering. |
(I'm not part of that group, but since you're asking on this thread...)
I hope not. It's the dependency that manages all other dependencies. nix
is probably the easiest / most reliable way for them to get software with
these complicated external dependencies installable by others.
…On Sat, Jun 3, 2017 at 1:24 PM, Roman Gonzalez ***@***.***> wrote:
Is there any way to use this library *without* using Nix? Are there plans
to remove that dependency later on in the roadmap? Just wondering.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACNoMZs3AhB5mlqSOO7FykRwG9pLxmMCks5sAZbXgaJpZM4NMdcM>
.
--
*(this message was composed with dictation: charitably interpret typos)Sam
Boosalis*
|
There's nothing preventing you from using this library without Nix. It's an ordinary Haskell library that we will eventually upload to Hackage once we are done polishing the library. The only manual bit you would need to manager yourself is installing the The main benefit of using Nix is that it takes care of installing exactly the right version of the |
yeah, the haskell library has the default Setup.hs, so its normal if it can
link. (i thought they meant a non-nix build script).
…On Sat, Jun 3, 2017 at 1:44 PM, Gabriel Gonzalez ***@***.***> wrote:
There's nothing preventing you from using this library without Nix. It's
an ordinary Haskell library that we will eventually upload to Hackage once
we are done polishing the library. The only manual bit you would need to
manager yourself is installing the grpc library dependency
The main benefit of using Nix is that it takes care of installing exactly
the right version of the grpc dependency for you without contaminating
global install paths
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACNoMX8EFIATmJSrW7Cf7xvJb7djGx2zks5sAZt-gaJpZM4NMdcM>
.
--
*(this message was composed with dictation: charitably interpret typos)Sam
Boosalis*
|
Thanks for your prompt reply Gabriel, I was not understanding what was the scope of the nix script, not familiar with the language and cannot easily infer the extent of what this nix scripts do. Perhaps having a place on the README.md that says what the nix file is installing for developers that are unfamiliar with Nix might help? Not a priority I understand, just my 2 cents... really looking forward to trying out this and the proto3-suite package. Cheers. |
The README does clarify what is being installed:
|
* Misc cleanup/refactor pass on test suite descriptions and structure (awakesecurity#13) * Rename module TestTypes => OldTestTypes * Rename test.proto and test_import.proto package names to GeneratedTestTypes and GeneratedImportedTestTypes respectively * +tests/Generated{,Imported}TestTypes.hs and related changes * Add (:: Int) annotation to enum bound to avoid default type warning in generated modules * (qcPropDecEncId test) Replace OldTestTypes types with GeneratedTestTypes types * Remove dependency on quickcheck-text * Add and support additional fields for `WithNesting` in test.proto We did this to match prior `NestedMsg` use in `OldTestTypes` as part of the effort of redirecting the test suite to operate on code generated from .protos rather than hand-rolled types. * Use GeneratedTestTypes for remainder of the current types under test (after making small tweaks for type parity) * Add pretty-show dep so it can be used in the repl * Fix bug in the `MessageField` instance for `PackedVec Word32` * Add helpers/instances for pprinting simplified, single-message DotProtos from corresponding Haskell types; comments * Minor module reorg * Remove warnings
errors with
ditto under
nix-shell
. afaict,release.nix
doesn't accept input. ghc obviously doesn't work, because they need the appropriate environment.i don't know how i should run the examples, so i'm gonna try them in a separate package.
i'm on:
if relevant.
The text was updated successfully, but these errors were encountered: