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

Attempt to fix the broken paths in config autogen #290

Merged
merged 1 commit into from
Jul 20, 2016

Conversation

cjepson
Copy link
Contributor

@cjepson cjepson commented Jul 19, 2016

The configuration autogenerator currently does not work well
and tries to read the sample file based on where the compiled
source's data directory was. This has been fixed so that the
most common directories where the sample configuration file
might be stored are searched. The configuration file is also
now generated in the correct place in Windows.

Fixes #289.

@alexlyp
Copy link
Member

alexlyp commented Jul 19, 2016

tACK dcrd and dcrctl

The configuration autogenerator currently does not work well
and tries to read the sample file based on where the compiled
source's data directory was. This has been fixed so that dcrd
only checks the %PROGRAMFILES% directory on Windows where the
sample configuration file might be stored. Configuration
autogeneration has been disabled for toehr operating systems.
@alexlyp alexlyp merged commit 525770d into decred:master Jul 20, 2016
@jcvernaleo jcvernaleo added this to the v0.2.0 milestone Jul 22, 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.

Dcrd looks for sample config in source files, not the installation directory.
3 participants