Post
Topic
Board Announcements (Altcoins)
Re: [ANN] Resurrection of Sprouts Classic
by
DZPrince
on 17/08/2018, 04:54:16 UTC
Godaddy is having issues right now but I think it should be up by tomorrow hopefully. I'll try to get it the process started tonight though since i have the domain and server already bought. I'll let you know when it's ready with the link

I just downloaded the Sprouts wallet source code to get an understanding of it.  Let me see if I can fix the 1 billion error and increase it to, like, 40 billion.  Also I will change it to be Sprouts Classic to be unique and independent from the failed HF wallet.

You should be able to increase this easily to 200 billion but I think the problem there is that it will require a hardfork of some sort.. I have tried similar before and it does stake but is orphaned every time.

Hi CryptoWiz420,

And this is what I want to prevent is another hard fork.  I just want to bring back Sprouts Classic for the community to benefit and fix any existing problems in the current wallet.  Right now I am having issues compiling now under QT Creator where it is for some reason spitting out an error that it cannot find the optionsdialog.moc file when I build the project.  I read all over the internet to try to find a solution for this and even re-installed QT Creator yesterday.  Let me see when I refresh the project.  I am currently compiling on a MacOS and will install QT Creator on my Windows 10 side to compile there.  I have installed Sourcetree to branch the current sprouts for others that want to pull my current project.
It seems this could be a missing link to some qt library, or something close to this.  Try these links to see if they have a solution:
https://stackoverflow.com/questions/4203122/qt-cannot-find-moc-file
https://askubuntu.com/questions/878130/qt-3-x-not-found-please-set-qt-include-qt-lib-moc-by-hand-on-my-ubuntu14-04
https://www.dash.org/forum/threads/darkcoin-qt-wont-link.1864/
https://stackoverflow.com/questions/15821663/what-is-the-lrt-flag-in-gnu-make



I actually added the following to the .pro file:

DESTDIR = bin
UI_DIR = .

CONFIG(debug, debug|release) {
        TARGET = sproutsclassic
        OBJECTS_DIR = build/sproutsclassic/debug
        MOC_DIR = build/sproutsclassic/debug
}

CONFIG(release, debug|release) {
        TARGET = sproutsclassic
        OBJECTS_DIR = build/sproutsclassic/release
        MOC_DIR = build/sproutsclassic/release
}

and made a slight change to a cpp file complaining about not finding the build.h file.  Now it will build further; however, I get the following error:

Undefined symbols for architecture x86_64:
  "RPCExecutor::reply(int, QString const&)", referenced from:
      RPCExecutor::request(QString const&) in rpcconsole.o
  "vtable for RPCExecutor", referenced from:
      RPCConsole::startExecutor() in rpcconsole.o
  NOTE: a missing vtable usually means the first non-inline virtual member function has no definition.
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [bin/SproutsClassic.app/Contents/MacOS/SproutsClassic] Error 1
00:50:50: The process "/usr/bin/make" exited with code 2.
Error while building/deploying project sprouts (kit: Desktop Qt 5.11.1 clang 64bit)
When executing step "Make"

I am still stumped on this one as I have been doing research online to see what is causing the specific error regarding the RPCExecutor.  Has anyone seen this error before?