Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Setting custom dictionaries through environment doesn't work #189
First, make sure that none of the open and closed issues is about the same issue as you are describing, and make sure to check the frequently asked questions in the README file.
If you're reporting a bug, use the template below. Otherwise, delete this template and write your issue normally.
Please select one:
Please select one:
My operating system:
OS version: ArchLinux
What was expected?
When building the package with
It's still pointing to the default directory.
@Edu4rdSHL (sorry, I followed you here from Freenode/#go-nuts)
The environment variables are only ever picked up from the runtime environment of the final application binary, and they can't be manipulated at compile time whatsoever.
To support building with embedded default values, cameradar will have to be updated to consult the environment and then look for a local package variable that's been defined by the compiler. That would look somewhat like this:
where then you could define
In absence of that, you'd usually set them like this (at runtime, not build time.)
Hello, @DHowett thank you much. I tried running with that syntax but seems that doesn't work also:
Also changing the GOPATH doesn't work.
The var is changed correctly but it's still pointing to src/ when according to https://github.com/Ullaakut/cameradar/blob/b62b431a54e6bb4b30df12d54c78792d2c1327b4/README.md#cameradar_custom_routes-cameradar_custom_credentials it should point to $GOPATH/dictionaries/
I'm on this, I might have introduced a regression with the
EDIT: Confirmed, the custom credentials and routes don't work using environment variables at the moment! Working on it
Found the origin of the issue. The way I changed the implementation made it so that the variables were using a dash separator instead of an underscore:
I'll push a