GröBkAz (OP)
|
|
July 31, 2013, 12:38:36 PM Last edit: July 31, 2013, 09:23:29 PM by GröBkAz |
|
Is there a good tutorial how to build the Litecoin qt client on windows? I can not believe how complicated it seems to compile a few files.
|
|
|
|
GröBkAz (OP)
|
|
July 31, 2013, 09:22:08 PM |
|
I pay 0.3 BTC each person that successfully explains to me: how to build a litecoin-qt client on a windows system. ->From the first download up to the final "ctrl-B command" in the Qt Creator. Is it even possible to build a litecoin or bitcoin wallet with Qt 5.1.0 creator?
|
|
|
|
shakezula
|
|
July 31, 2013, 09:31:52 PM |
|
You don't want to do it in Qt creator. You want to install the command line bits and do it that way. Trust me, I tried for WEEKS to get this to work in the creator. I've made it exceedingly easy to compile for windows with this guide: http://devtome.com/doku.php?id=scrypt_altcoin_cloning_guide#windows_-qtThe list of things you should install (MinGW, QT Command-line, Perl) and links to them are in the guide. For the dependecnies, you can download my pre-compiled dependencies here: https://github.com/foocoin/deps/archive/master.zipThe zip should be placed as c:\deps. Now, open your -qt.pro with Notepad or whatever, and replace this line: DEFINES += QT_GUI BOOST_THREAD_USE_LIB BOOST_SPIRIT_THREADSAFE with this one: DEFINES += QT_GUI BOOST_THREAD_USE_LIB BOOST_SPIRIT_THREADSAFE BOOST_THREAD_PROVIDES_GENERIC_SHARED_MUTEX_ON_WIN __NO_SYSTEM_INCLUDES Its right at the top, very easy to find, 4th or 5th line down. Now right under that there will be a section that looks like this: # Dependency library locations can be customized with: # BOOST_INCLUDE_PATH, BOOST_LIB_PATH, BDB_INCLUDE_PATH, # BDB_LIB_PATH, OPENSSL_INCLUDE_PATH and OPENSSL_LIB_PATH respectively Replace that with this: windows:LIBS += -lshlwapi LIBS += $$join(BOOST_LIB_PATH,,-L,) $$join(BDB_LIB_PATH,,-L,) $$join(OPENSSL_LIB_PATH,,-L,) $$join(QRENCODE_LIB_PATH,,-L,) LIBS += -lssl -lcrypto -ldb_cxx$$BDB_LIB_SUFFIX windows:LIBS += -lws2_32 -lole32 -loleaut32 -luuid -lgdi32 LIBS += -lboost_system-mgw46-mt-sd-1_53 -lboost_filesystem-mgw46-mt-sd-1_53 -lboost_program_options-mgw46-mt-sd-1_53 -lboost_thread-mgw46-mt-sd-1_53 BOOST_LIB_SUFFIX=-mgw46-mt-sd-1_53 BOOST_INCLUDE_PATH=C:/deps/boost BOOST_LIB_PATH=C:/deps/boost/stage/lib BDB_INCLUDE_PATH=c:/deps/db/build_unix BDB_LIB_PATH=c:/deps/db/build_unix OPENSSL_INCLUDE_PATH=c:/deps/ssl/include OPENSSL_LIB_PATH=c:/deps/ssl MINIUPNPC_LIB_PATH=c:/deps/miniupnpc MINIUPNPC_INCLUDE_PATH=c:/deps Then you'll be able to do the "qmake" and "make -f Makefile.Release" as listed in the step by step guide. I'm happy to walk you through this in irc if you'd like, my BTC addy is in my sig.
|
|
|
|
GröBkAz (OP)
|
|
July 31, 2013, 10:29:18 PM |
|
don't work. :-(
I had the same problem like on the toutorial from nitrogenetics.
C:\coins\LiteCoin-master>qmake "USE_UPNP=- LiteCoin-qt.pro Project MESSAGE: Building without UPNP support Project MESSAGE: Building with UPNP supportRemoved plural forms as the target la nguage has less forms. If this sounds wrong, possibly the target language is not set or recognized. Project MESSAGE: Building without UPNP support Project MESSAGE: Building with UPNP supportRemoved plural forms as the target la nguage has less forms. If this sounds wrong, possibly the target language is not set or recognized. Project MESSAGE: Building without UPNP support Project MESSAGE: Building with UPNP supportRemoved plural forms as the target la nguage has less forms. If this sounds wrong, possibly the target language is not set or recognized.
the release and debug folders are empty
|
|
|
|
shakezula
|
|
July 31, 2013, 11:12:46 PM |
|
don't work. :-(
I had the same problem like on the toutorial from nitrogenetics.
C:\coins\LiteCoin-master>qmake "USE_UPNP=- LiteCoin-qt.pro Project MESSAGE: Building without UPNP support Project MESSAGE: Building with UPNP supportRemoved plural forms as the target la nguage has less forms. If this sounds wrong, possibly the target language is not set or recognized. Project MESSAGE: Building without UPNP support Project MESSAGE: Building with UPNP supportRemoved plural forms as the target la nguage has less forms. If this sounds wrong, possibly the target language is not set or recognized. Project MESSAGE: Building without UPNP support Project MESSAGE: Building with UPNP supportRemoved plural forms as the target la nguage has less forms. If this sounds wrong, possibly the target language is not set or recognized.
the release and debug folders are empty
This is on the right track, you can ignore these warnings. If you used m compilation deps, you can even leave the UPNP part off. Try this: qmake litecoin-qt.pro then ignore the errors about if this seems wrong blah blah. Then do: make -f Makefile.Release and your coins should build in to the release folder.
|
|
|
|
Petr1fied
|
|
July 31, 2013, 11:33:33 PM |
|
don't work. :-(
I had the same problem like on the toutorial from nitrogenetics.
C:\coins\LiteCoin-master>qmake "USE_UPNP=- LiteCoin-qt.pro Project MESSAGE: Building without UPNP support Project MESSAGE: Building with UPNP supportRemoved plural forms as the target la nguage has less forms. If this sounds wrong, possibly the target language is not set or recognized. Project MESSAGE: Building without UPNP support Project MESSAGE: Building with UPNP supportRemoved plural forms as the target la nguage has less forms. If this sounds wrong, possibly the target language is not set or recognized. Project MESSAGE: Building without UPNP support Project MESSAGE: Building with UPNP supportRemoved plural forms as the target la nguage has less forms. If this sounds wrong, possibly the target language is not set or recognized.
the release and debug folders are empty
This is on the right track, you can ignore these warnings. If you used m compilation deps, you can even leave the UPNP part off. Try this: qmake litecoin-qt.pro then ignore the errors about if this seems wrong blah blah. Then do: make -f Makefile.Release and your coins should build in to the release folder. If only it were that simple. I've tried every guide under the sun (including yours) and despite best efforts it always fails at the exact same point. That's why i just gave up trying and ask you nowadays. daemons, no problem, Windows QT urghhh.
|
|
|
|
shakezula
|
|
July 31, 2013, 11:35:23 PM |
|
Where does it die at?
|
|
|
|
Petr1fied
|
|
July 31, 2013, 11:48:36 PM |
|
This is where it breaks: ..\Qt\4.8.4\include/boost/system/error_code.hpp:216:36: warning: 'boost::system: :native_ecat' defined but not used [-Wunused-variable] mingw32-make: *** [build/bitcoin.o] Error 1 No idea why but everything I've ever tried results in it failing here. (tested with barcoin)
|
|
|
|
shakezula
|
|
August 01, 2013, 12:03:36 AM |
|
This is where it breaks: ..\Qt\4.8.4\include/boost/system/error_code.hpp:216:36: warning: 'boost::system: :native_ecat' defined but not used [-Wunused-variable] mingw32-make: *** [build/bitcoin.o] Error 1 No idea why but everything I've ever tried results in it failing here. (tested with barcoin) Hmmm, I think that's sorted by adding __NO_SYSTEM_INCLUDES to the DEFINES= list, note that is 2 _ _ 's there, not sure why. Though if you tried it with the BARCoin source, the -qt.pro should already have this I think...looking back through the threads I found this from you: https://bitcointalk.org/index.php?topic=149479.msg2091689;topicseen#msg2091689And it would show you don't have -D__NO_SYSTEM_INCLUDES or -D_BOOST_THREAD_PROVIDES_GENERIC_SHARED_MUTEX_ON_WIN in your compile. Try adding them to the -qt.pro or to the Makefile.Release directly and give it another compile?
|
|
|
|
GröBkAz (OP)
|
|
August 01, 2013, 07:23:17 AM |
|
This is where it breaks: ..\Qt\4.8.4\include/boost/system/error_code.hpp:216:36: warning: 'boost::system: :native_ecat' defined but not used [-Wunused-variable] mingw32-make: *** [build/bitcoin.o] Error 1 No idea why but everything I've ever tried results in it failing here. (tested with barcoin) Hmmm, I think that's sorted by adding __NO_SYSTEM_INCLUDES to the DEFINES= list, note that is 2 _ _ 's there, not sure why. Though if you tried it with the BARCoin source, the -qt.pro should already have this I think...looking back through the threads I found this from you: https://bitcointalk.org/index.php?topic=149479.msg2091689;topicseen#msg2091689And it would show you don't have -D__NO_SYSTEM_INCLUDES or -D_BOOST_THREAD_PROVIDES_GENERIC_SHARED_MUTEX_ON_WIN in your compile. Try adding them to the -qt.pro or to the Makefile.Release directly and give it another compile? So, I tried your tutorial on your master-coin and it works...juhu so I tried the same on a other coin litecoin and feathercoin: make -f makefile.release ..\..\deps\boost/boost/system/error_code.hpp: Im globalen Gültigkeitsbereich: ..\..\deps\boost/boost/system/error_code.hpp:214:36: Warnung: »boost::system::po six_category« definiert, aber nicht verwendet [-Wunused-variable] ..\..\deps\boost/boost/system/error_code.hpp:215:36: Warnung: »boost::system::er rno_ecat« definiert, aber nicht verwendet [-Wunused-variable] ..\..\deps\boost/boost/system/error_code.hpp:216:36: Warnung: »boost::system::na tive_ecat« definiert, aber nicht verwendet [-Wunused-variable] mingw32-make: *** [build/bitcoin.o] Error 1 the same error again. I added __NO_SYSTEM_INCLUDES on the DEFINES=list
|
|
|
|
xisalty
Newbie
Offline
Activity: 42
Merit: 0
|
|
August 08, 2013, 06:26:06 AM |
|
Which version of Qt would you like a guide written for ? I've found that as of now Qt 5.1.0 is incompatible.
|
|
|
|
muddafudda
Legendary
Offline
Activity: 1008
Merit: 1022
|
|
August 08, 2013, 07:18:41 AM Last edit: August 08, 2013, 01:55:03 PM by muddafudda |
|
I know this error. Hmm
|
|
|
|
muddafudda
Legendary
Offline
Activity: 1008
Merit: 1022
|
|
August 12, 2013, 08:49:06 AM |
|
Will do this for .3BTC in PM only.
|
|
|
|
y0m0
Newbie
Offline
Activity: 20
Merit: 0
|
|
August 12, 2013, 08:59:42 AM |
|
have you tried this? LWm5odgHrb1XjxSHa5Mt9m3Gbiqr3Y6Pm5
|
|
|
|
xisalty
Newbie
Offline
Activity: 42
Merit: 0
|
|
August 12, 2013, 05:28:37 PM |
|
have you tried this? LWm5odgHrb1XjxSHa5Mt9m3Gbiqr3Y6Pm5 I thought the post was focused on getting instructions on how to build the client.
|
|
|
|
|