Hi

I was not able to dump the errors to file at the moment of sending my previous mail, because the command line window does not allow me to dump them (because of the spaces in the compile command). In the meantime, I have been searching further on and it seems that when you let the tdm installer (tdm-gcc-4.5.0.exe) do its job, it does not set the right path variable. mingwenv refers to "c:\mingw" but "c:\MinGW32" was created by the installer. Possibly this was the only problem (hence the wiki page http://wiki.inkscape.org/wiki/index.php/Win32Port needs some updating). I'm compiling inkscape at the moment.

Regards Kris

buildtool.cpp: At global scope: buildtool.cpp:9098: error: expected class-name before '{' token buildtool.cpp:9101: error: expected ')' before '&' token buildtool.cpp:9112: error: 'Element' has not been declared buildtool.cpp:9124: error: expected constructor, destructor, or type conversion before '*' token buildtool.cpp: In constructor 'buildtool::TaskCopy::TaskCopy()': buildtool.cpp:7194: error: no matching function for call to 'buildtool::Task::Ta sk()' buildtool.cpp:6753: note: candidates are: buildtool::Task::Task(const buildtool: :Task&) buildtool.cpp:6747: note: buildtool::Task::Task(buildtool::MakeB ase&) buildtool.cpp: At global scope: buildtool.cpp:7202: note: synthesized method 'buildtool::TaskCopy::TaskCopy()' f irst required here

2010/6/19 Krzysztof Kosiński <tweenk.pl@...400...>:

2010/6/18 Kris De Gussem <kris.degussem@...400...>:

...

Building buildtool.cpp fails.

What are the error messages?

Regards, Krzysztof

W dniu 20 czerwca 2010 23:21 użytkownik Kris De Gussem <kris.degussem@...400...> napisał:

There was some crap at the end of the previous mail (from the time I did not rename the mingw path). I had one compilation error:

The error is a const mismatch. Try replacing line 736 in src/extension/internal/emf-win32-inout.cpp:

myEnhMetaFileProc(HDC /*hDC*/, HANDLETABLE * /*lpHTable*/, ENHMETARECORD *lpEMFR, int /*nObj*/, LPARAM lpData)

with:

myEnhMetaFileProc(HDC /*hDC*/, HANDLETABLE * /*lpHTable*/, ENHMETARECORD const *lpEMFR, int /*nObj*/, LPARAM lpData)

Uwe: buildtool builds on a best effort basis, trying to compile everything it can before stopping. To see the errors, you need to run buildtool again; it will only try to rebuild the files that had errors. You can capture this log to a file by running buildtool like this: buildtool 2> log.txt

Regards, Krzysztof

W dniu 26 czerwca 2010 04:12 użytkownik Chris Morgan <chris.morganiser@...400...> napisał:

Last time I used it, before the new devlibs which shouldn't have changed anything, buildtool writes its output to a file already; the filename was compile.lst or something like that. Also on Windows 2> won't work; that would run "buildtool 2" and put its output in log.txt. It would be buildtool > log.txt or buildtool>log.txt for Windows. stderr will be caught automatically, I believe. Windows' separation of them is less precise than other operating systems'.

You are wrong. http://support.microsoft.com/kb/110930

Even 2>&1 works. (I was surprised too.)

Regards, Krzysztof

2010/6/28 Uwe Schöler <mail@...2227...>:

Hi Krzysztof,

i get no error message at all.

The building process is ending at s -Isrc/xml src/xml/subtree.cpp -o build/obj/xml/subtree.o

what can i change to get a result?

Sincerely,

UweSch

If you ran the buildtool with a command like: buildtool 2>log.txt then the error messages should be in the log.txt file. They won't be displayed on the screen.

Regards, Krzysztof