Topic: Building headless Bitcoin and Bitcoin-qt on Windows - page 36. (Read 419389 times)

Thanks for these instructions. This helped quickly get a solid build/dev environment up and running.

So I checked in c:/deps/db-4.8.30.NC/build_unix I couldn't find db_cxx.a, did I build it wrong?  I also ran a full HD search and found nothing.  Thanks for your help!

Nice ive looking for this. Can this be done on a VPS.

i am testing to creat the bitcoin wallte
now i was completed those command
no error

then i dont know how to creat the bitcoin-qt.exe 
i am try to use this command:

who was know how to build it?
please told me
thanks very much!

What parts are you referring to? I think I clearly stated that configuring the build environment on a clean vm is recommended. As you are using gcc-3.4.4-3-msys I suggest you remove C:\MinGW completely and reinstall MinGW by selecting only the packages mentioned at step 1.1 (msys-base-bin, msys-autoconf-bin, msys-automake-bin, msys-libtool-bin).

when I run gcc -v from inside mingw32.bat I get this

 
Let's try again,

Did you see my message above?  I made it bigger this time   So when one sees a gcc argument like -ldb_cxx one should find a file named libdb_cxx.a there.  Notice how -lssl becomes libssl.a, etc.

Hint: one must observe and generalize from the patterns shown in the makefile.  It's all there if one just looks. Perhaps this has helped others.

Ron

I can find db_cxx.h in the "BDB_LIB_PATH=c:/deps/db-4.8.30.NC/build_unix" and when I built Berkeley DB I used --enable_cxx

If one studies the makefile, one sees that the -lxxx refers to a file in the -LpathWhateverDirectory whose name is libxxx.a

So do you have such a file in that place?  If not, then either it wasn't built, or was built but put elsewhere (or erased, renamed,...)  Can't think of too many orther possibilities

Ron

Which guide?  We have at least two here that I know of?
Saying it should isn't enough.  One should be able to "inject a line" anywhere in any batch file like this:
gcc -v
and you should see this response:
Or some such.  Where the version, model, etc. may vary.  If you don't see that then you have to find out why.  And fix it

Ron

Ron, thanks for the reply, I followed this guide and I am not sure if it's all set up correctly as some of the guide is very unclear and very confusing but I have everything installed and im on windows 8.1 and gcc should be in all the paths so im a bit confused about it all as to why it won't find gcc.exe

at make -f makefile.release I get In the .pro file the path BDB_LIB_PATH point to the directory with db_cxx.h
also, how to I get a log from make?

Hello Stygian,

I think he's saying that you can get a MinGW at the link given, FWIW.

Looking at your code output above, note the bold line!  It is saying to me that when you ran your build program, whatever it may be,  your Operating System, whatever it may be (Windows of some flavor, I presume), couldn't find gcc.exe.  It is your task to determine why it (the OS) couldn't find gcc.exe.  Hint: it looks first in the current directory, then in all the directories in the path environment variable.  If it still can't find gcc.exe you will see the above message.  The path is the path that exists when and where the build program is run.  Perhaps not the path when the build program ends?  Paths are dependent upon which user for example, is logged on, etc.

Ron

I have no clue what you just said, can you repeat that in english

Succes!

Three days ago I did not know about boost or perl, and I still don't really, but now I have a working bitcoin wallet!

Amazing, thanks a lot!


 

Hello Dan,

Thanks for the kind words.  I wanted to respond, but it seems your post, which was #476 as I remember, is gone!  I've seen that happen when editing a response.

Just an update on the MSVC++ project.  The code is good,  runs in debug or release, doesn't abort on illegal C++ code anymore.  The only issue is that it needs to "conform" to the "bitcoin standard" as to what is a legitimate transaction.  It seems that in block 284,028 ~2/4/2014 there was a transaction that there is a disagreement about the legality between gcc bitcoind.exe and MSVC bitcoind.exe.  I need to find that discrepancy.  I don't know how to go about that just yet, but like all things "bitcoin" there should be a way.

Ron

I sent you a PM

I am the lead of a new altcoin team, AppleBytes.

I successfully compiled the windows wallet, but it crashes when started.

Are you or anyone else on this thread interested in helping?

Payment will be made in Bitcoin.

We are also looking for help with the MAC wallet, I compiled it and it runs on my MAC, but not other peoples.
And are looking for someone to develop a pool server.

Details on AppleBytes here: Announce Thread

Hello GivecoinDan

Looking at message #466 (https://bitcointalksearch.org/topic/m.5627966), note that g++ is looking to link leveldb stuff using -L"C:/testcoin/src/leveldb", which is what I hi-lited in message #470.

If you "mix" leveldb "src" trees from MAXCoin, Litecoin etc., are you sure you have the same versions (of leveldb) among the sources and libraries?  I don't think that the code has changed from levelDB 1.9 to 1.12 to 1.15 but I'm not sure.

Also, note that the "include" lines in the bitcoin leveldb.h & leveldb.cpp sources are like this:

and


which means that the "include path" the gcc needs to see is
-IC:/testcoin/src/leveldb/include -IC:/testcoin/src/leveldb/helpers as in message #466

But if you are creating those libraries, then you need an additional path of -IC:/testcoin/src/leveldb so that the leveldb source files can "find each other" in their includes! See block_builder.cc for example, which looks like:


All pretty long-winded, but the idea is that if one builds the libleveldb.a & libmemenv.a with some code, one should check what it is compiling and what it is putting where?  

Of course, all of this nonsense vanishes when one just compiles and links one's Bitcoin or *coin sources in MSVC++  I have a set of multi-threaded static libraries placed where I please, and I just point MSVS at them and it figures out all the details!  I will announce here that I have compiled and ran daemons successfully for Bitcoin, Maxcoin, Auroracoin and YACoin all using the same libraries, that were built once and then one basically forgets about them.  Ah, full screen debugging  Here's a  hint:

Consider the line of code from bitcoin's (*coin's?) CScriptCompressor class member function Serialize() in script.h:

s << CFlatData(&script[0], &script[script.size()]);

What happens, or should happen, when:
1. one references &script[0] and script.size() is 0?
2. one references script[script.size()] when script.size() is any value including 0?

The answer is that what happens is unknown!!!

At least according to my reading on vector templates.  And sure enough, P.J. Plauger agrees when running in debug mode (LOL).  How many years has "loose" vector<> (especially), list<> and map<> code been in the Bitcoin sources?  Four years.  I think it is time to make the code correct, don't you think?

Ron

i dont have it.are u mean this?http://sourceforge.net/projects/mingwbuilds/files/latest/download

Interesting, keep us informed



Make sure mingw-builds is in path then check that your gcc -v output and the one specified at step 1.6 are the same.