The build for Mac OS X of course produces an app bundle (Bitcoin Qt.app). However, I was wondering if there is a way to pass parameters to this app by default when it launches, rather than just manually on the command line. I looked at the configure script, but I don't think it has the capabilities for this.
-
alexreg commented at 10:48 PM on April 7, 2016: contributor
-
paveljanik commented at 5:43 AM on April 8, 2016: contributor
Yes, use its config file - see https://github.com/bitcoin/bitcoin/blob/master/doc/build-osx.md#running
Please close this issue.
-
alexreg commented at 12:09 PM on April 8, 2016: contributor
What if the config file is in a non-standard location? Such as
/Library/Application Support/Bitcoin/bitcoin.conf. -
theuni commented at 6:20 PM on April 8, 2016: member
What params do you want to pass? If you're looking in configure, I assume you want to hard-code something for all runs?
-
alexreg commented at 6:22 PM on April 8, 2016: contributor
Yeah. -conf, -datadir, and -pid are teh params I want to “hard-code” for the app bundle.
On 8 Apr 2016, at 19:21, Cory Fields notifications@github.com wrote:
What params do you want to pass? If you're looking in configure, I assume you want to hard-code something for all runs?
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub #7836 (comment)
-
theuni commented at 6:27 PM on April 8, 2016: member
Hmm, that's a pretty scary idea. I'd rather not make it easier for some altcoin to clobber our data. What's the rationale behind changing those?
-
alexreg commented at 6:32 PM on April 8, 2016: contributor
Because I’m getting MacPorts to install Bitcoin core and the daemon to /opt/local, and a launchd plist to /Library/LaunchDaemons. The data dir / log file / pid file will be under standard Unix directories in /opt/local (the MacPorts prefix). I want the GUI to recognise this, and thus get the correct config to connect to the daemon… unless the GUI is meant to have different data dir / log file / pid paths from the daemon? I presume the daemon and GUI do read the same log file / data dir though, since they use it to get the RPC credentials?
On 8 Apr 2016, at 19:28, Cory Fields notifications@github.com wrote:
Hmm, that's a pretty scary idea. I'd rather not make it easier for some altcoin to clobber our data. What's the rationale behind changing those?
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub #7836 (comment)
- laanwj added the label MacOSX on Apr 11, 2016
-
jonasschnelli commented at 1:46 PM on April 11, 2016: contributor
Hardcode parameters is not something we want in master. It could make sense that you patch bitcoin-core/-qt if you plan to deploy it over a package manager like MacPorts. Maybe you can patch the Info.plist and pass some argument without actually modifying the bitcoin-qt binary.
Closing.
- jonasschnelli closed this on Apr 11, 2016
-
alexreg commented at 2:46 PM on April 11, 2016: contributor
Yeah, that’s my solution in the end. Thanks.
On 11 Apr 2016, at 14:47, Jonas Schnelli notifications@github.com wrote:
Hardcode parameters is not something we want in master. It could make sense that you patch bitcoin-core/-qt if you plan to deploy it over a package manager like MacPorts. Maybe you can patch the Info.plist and pass some argument without actually modifying the bitcoin-qt binary.
Closing.
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub #7836 (comment)
- DrahtBot locked this on Sep 8, 2021
Contributors
Labels