Page 3 of 3
Posted: Wed Sep 23, 2009 3:00 pm
Alright, here it is.
I omitted -d.
Posted: Wed Sep 23, 2009 4:40 pm
OK... so here's the fun part. The contents of that file are the actual command that will be used when making the library. So start running them.... yeah, this will take a while.
Maybe change the filename of that output.txt to output.bat so that when it fails you'll see the last instruction.
We need to know which instruction fails so we can figure out which program is having an issue.
The good new is that by doing this, you WILL actually be starting the build process. So if you get to the end of the file and no errors, then congrats you just built the library and I will have no idea why.
Let me know which line exactly causes an issue.
Posted: Fri Sep 25, 2009 10:03 am
Okay, I executed the output file as a .bat (of course on the windows command line).
He did lots of command lines without error.
At the end it executed a very long line, printed the message
"Line is too long" and finished.
I'm not aware of any error messages, and I cannot copy the whole shell output, since I am not able to scroll.
Enclosed, the last output I could copy.
After the whole process, I've got lots of Object Files (.o)
and .o.d files in the new directory ..\build\msw\gcc_mswud .
Posted: Fri Sep 25, 2009 1:02 pm
OK, here's the good news: if you have the object files then you have compiled most of the wxWidgets code.
Here's the bad news: the CMD line can't do the final linking/compiling because it has to list ALL of those object files in one command! (hence why we use mingw32-make in the first place!)
So now we know that the problem lies in the make system. Go ahead and give it a try with the mingw32-make -d ...
That way it should tell us which make statement is calling some program. Oh, and if the output gets too long, then just append the "> output.txt" to save the output in the file.
Posted: Mon Sep 28, 2009 10:34 am
I'm sorry, but I don't understand the next move; what shall I execute now??
Posted: Mon Sep 28, 2009 1:10 pm
Code: Select all
mingw32-make -d -f makefile.gcc SHARED=0 BUILD=debug UNICODE=1 MONOLITHIC=1 CFG="" VENDOR="" > output.txt
Remember to put the -d in this time. Supposedly this will show you each command and it's output, so let's see which command caused the issue.
I believe mingw is setup with something interesting. I'm trying to see if there is an environment variable or other config item that is causing make to run something that doesn't even exist.
Posted: Thu Oct 01, 2009 11:09 am
Here is the Output by command line.
Code: Select all
C:\Programmierung\cpp_libs\wxWidgets-2.8.10\build\msw>mingw32-make -d -f makefile.gcc SHARED=0 BUILD=debug UNI
CODE=1 MONOLITHIC=1 CFG="" VENDOR="" > output.txt
Der Befehl "C:\DOKUME~1\FLO" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
mingw32-make: *** [..\..\lib\gcc_lib\mswud] Error 1
Output File is about 10mb now, i will upload it in parts later.
EDIT: 3/22 up