Topic: Bitcoin client clone on Linux trying to modify files (Read 158 times)
For those searching for this in the future, you have to compile the bitcoind or zcashd or whatever your daemon file is after modifying the files in the /src folder. You can do this by modifying and saving the files you need edited, and then running the make file in the /src directory where the bitcoind file is located. In other words, if using the command line, then and you will see the compiler compile any files that were modified. Hope this helps!
I haven't been able to find much info probably because I just cant figure out the correct search terms, but I have been learning about pools and the bitcoin core client etc. My problem is that as I change my bitcoin clone client source files on my Linux machine, it seems to have no effect on my mining pool. For instance, I changed the block decode error messages in the source files so I could see exactly where in the code that error was being generated, but I still get the original unaltered error message in the NOMP logs. I know to stop and restart my coin daemon after each change as well as the pool if I make any changes there. So is the code being executed on the remote peer end when a block is submitted or when gbt is called? Or does the client run the code straight from the github repo somehow so its always up to date? Please forgive me if I am asking questions that are common knowledge, but I seem to be at a roadblock as far as learning all this on my own and from reading online. Thanks in advance for any help or suggested reading.
-Mike
-Mike
Jump to: