Quote from: zvs on April 28, 2014, 10:32:01 PM

Quote from: meelvanchris on April 28, 2014, 07:22:10 PM

Ok. I'm officially stuck again. Daemon compiled. Tested and working! yay! (ty) Now the Qt.
Working with 0.6.3 coin ( i know i really shouldnt =) But ive started and made it this far... Also best way to learn i think. So hope ull bear with me for little while longer.... Also studied up on litecoin-qt.pro posted here : https://bitcointalk.org/index.php?topic=149479.msg5568805#msg5568805

So im pretty sure my problem is not there. whenever i try to build qt. (using 4.8.5) it stops at the *.o files.

Code:

g32 -lQtCore -lole32 -luuid -lws2_32 -ladvapi32 -lshell32 -luser32 -lkernel32
./build\bitcoingui.o: file not recognized: File format not recognized
collect2.exe: error: ld returned 1 exit status

Tried many different things. Including just plain copying the required o-file from a similar build. And then it accepts it. And goes to the next error :

Code:

g32 -lQtCore -lole32 -luuid -lws2_32 -ladvapi32 -lshell32 -luser32 -lkernel32
./build\optionsdialog.o: file not recognized: File format not recognized
collect2.exe: error: ld returned 1 exit status

Untill i run out of *.o files to copy.... (and plain copying is ofc not a solution, but helps me as means to an end to narrowing down the problem)

So is my build corrupted somehow? (daemon works) Is my Qt incompatible? Is there any way to get Qt/mingw32-make to tell me in more detail exactly what error's it encountered? Any info on how to proceed, or in witch direction to look would be much appreciated.

first off, what's up with ./build\optionsdialog.o? i've never compiled anything in windows, so i dunno if it's supposed to look like that or not. but shouldn't it be .\build\optionsdialog.o?

./build\whatever in a normal windows environment wouldn't work (ed: well, ./xxx would work, but it wouldn't work for a directory change, as in ./xxx\xxx)

fixed the damn slashes

I think that is a result of Linux style path naming of MSYS and Windows style recursion in the makefile (I guess). Nothing to worry about, Windows will generally accept both styles.