Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Community » Newbie corner » How view full build log?
How view full build log? [message #58526] Wed, 08 June 2022 12:35 Go to next message
neo_in_matrix is currently offline  neo_in_matrix
Messages: 24
Registered: May 2022
Promising Member
I have a weird build error when a package has a windows RC file. But the build log pane at bottom only shows a generic "There were errors" message. How do I view a full build log?
index.php?t=getfile&id=6609&private=0
Re: How view full build log? [message #58527 is a reply to message #58526] Wed, 08 June 2022 12:37 Go to previous messageGo to next message
neo_in_matrix is currently offline  neo_in_matrix
Messages: 24
Registered: May 2022
Promising Member
CONT.

The weird part is that I only get this error with 32-bit compilers (except the bundled CLANG 32-bit). I tried some tweaking like below, but it did not work.
index.php?t=getfile&id=6610&private=0
  • Attachment: u++clopt.PNG
    (Size: 21.76KB, Downloaded 183 times)
Re: How view full build log? [message #58530 is a reply to message #58527] Wed, 08 June 2022 20:55 Go to previous messageGo to next message
Klugier is currently offline  Klugier
Messages: 1077
Registered: September 2012
Location: Poland, Kraków
Senior Contributor
Hello,

On the main TheIDE toolbar select "Setup -> Be verbose". Please let me know if you will get more reasonable error output on the console.
index.php?t=getfile&id=6611&private=0

Klugier


U++ - one framework to rule them all.
Re: How view full build log? [message #58533 is a reply to message #58530] Thu, 09 June 2022 05:07 Go to previous message
neo_in_matrix is currently offline  neo_in_matrix
Messages: 24
Registered: May 2022
Promising Member
It seems I had a wrong BM configured.

After turning on "Be verbose" I see that TheIDE is invoking "i686-w64-mingw32-c++-windres.exe" which does not exit.

The "Compiler name" filed should be empty because other compilers except the bundled CLANGs do not have strict i686-w64-mingw32-c++ prefix. Thus they do not have i686-w64-mingw32-c++-windres.exe and hence causing the build error.

But the error is still quite misleading because it does not state that it could not find the expected executable. It only reports there were errors and did not even mention where was wrong.
----- SQLite ( MAIN GCC DEBUG DEBUG_FULL WIN32 )
cd C:\Build\test\upp\purec\SQLite
sqlite3.rc
i686-w64-mingw32-windres.exe -i "C:\Build\test\upp\purec\SQLite\sqlite3.rc" -o "C:/Build/test/upp/purec/out/purec/S
    QLite/winlibs32.Debug.Debug_Full.Main.Noblitz\sqlite3.rc$rc.o" --include-dir="C:\Build\test\upp\purec" --includ
    e-dir="C:\apps\gnu\upp/uppsrc" --include-dir="C:/Build/test/upp/purec/out/purec/SQLite/winlibs32.Debug.Debug_Fu
    ll.Main.Noblitz" -DflagMAIN -DflagGCC -DflagDEBUG -DflagDEBUG_FULL -DflagWIN32 -D_DEBUG
compiled in (0:00.00)
shell.c
i686-w64-mingw32-c++ -c  -I"C:\Build\test\upp\purec" -I"C:\apps\gnu\upp/uppsrc" -I"C:/Build/test/upp/purec/out/pure
    c/SQLite/winlibs32.Debug.Debug_Full.Main.Noblitz" -DflagMAIN -DflagGCC -DflagDEBUG -DflagDEBUG_FULL -DflagWIN32
     -ggdb -g2 -static   -fexceptions -D_DEBUG -O0 -x c "C:\Build\test\upp\purec\SQLite\shell.c"  -o "C:/Build/test
    /upp/purec/out/purec/SQLite/winlibs32.Debug.Debug_Full.Main.Noblitz\shell.c.o"
compiled in (0:00.04)
sqlite3.c
i686-w64-mingw32-c++ -c  -I"C:\Build\test\upp\purec" -I"C:\apps\gnu\upp/uppsrc" -I"C:/Build/test/upp/purec/out/pure
    c/SQLite/winlibs32.Debug.Debug_Full.Main.Noblitz" -DflagMAIN -DflagGCC -DflagDEBUG -DflagDEBUG_FULL -DflagWIN32
     -ggdb -g2 -static   -fexceptions -D_DEBUG -O0 -x c "C:\Build\test\upp\purec\SQLite\sqlite3.c"  -o "C:/Build/te
    st/upp/purec/out/purec/SQLite/winlibs32.Debug.Debug_Full.Main.Noblitz\sqlite3.c.o"
compiled in (0:00.00)
C:\apps\gnu\winlibs\mingw32\bin\i686-w64-mingw32-c++.exe -c  -I"C:\Build\test\upp\purec" -I"C:\apps\gnu\upp/uppsrc"
     -I"C:/Build/test/upp/purec/out/purec/SQLite/winlibs32.Debug.Debug_Full.Main.Noblitz" -DflagMAIN -DflagGCC -Dfl
    agDEBUG -DflagDEBUG_FULL -DflagWIN32 -ggdb -g2 -static   -fexceptions -D_DEBUG -O0 -x c "C:\Build\test\upp\pure
    c\SQLite\shell.c"  -o "C:/Build/test/upp/purec/out/purec/SQLite/winlibs32.Debug.Debug_Full.Main.Noblitz\shell.c
    .o"
C:\apps\gnu\winlibs\mingw32\bin\i686-w64-mingw32-c++.exe -c  -I"C:\Build\test\upp\purec" -I"C:\apps\gnu\upp/uppsrc"
     -I"C:/Build/test/upp/purec/out/purec/SQLite/winlibs32.Debug.Debug_Full.Main.Noblitz" -DflagMAIN -DflagGCC -Dfl
    agDEBUG -DflagDEBUG_FULL -DflagWIN32 -ggdb -g2 -static   -fexceptions -D_DEBUG -O0 -x c "C:\Build\test\upp\pure
    c\SQLite\sqlite3.c"  -o "C:/Build/test/upp/purec/out/purec/SQLite/winlibs32.Debug.Debug_Full.Main.Noblitz\sqlit
    e3.c.o"
SQLite: 2 file(s) built in (0:06.95), 3477 msecs / file

There were errors. (0:06.96)

[Updated on: Thu, 09 June 2022 05:11]

Report message to a moderator

Previous Topic: How find files by name?
Next Topic: Cannot compile PromptOK(inputBox.GetText())
Goto Forum:
  


Current Time: Tue Jun 25 21:28:44 CEST 2024

Total time taken to generate the page: 0.01819 seconds