Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
log filename including compiler, version, linker and debug or release ?
BlueHazzard:
--- Quote from: stahta01 on October 28, 2019, 07:14:26 pm ---Did you check the codeblocks tab instead of the build log tab?
--- End quote ---
As Tim noted, the "log" message of the command
--- Code: ---[[Log(_("Test"))
--- End code ---
should appear in the "Code::Blocks" of the "logs&others" view. If not, you put things in the wrong place...
Again as Tim noted the right place is Project->Build options->Select the project name on the right side->Pre/post build steps->Post build steps
Maybe you can make a screenshot of the dialog?
pabristow:
Ah - I see - I was expecting to see "test" in the Build Log tab.
But I only have Build Log and Build messages tabs (I deleted the others on the grounds that they were not useful to me). Perhaps a mistake :-(
How do I restore to get the Code::blocks tab in Logs and Others?
PS I think I have the command in the right place, but not seeing the output from it. And perhaps I need to RTFM on scripting (I hoped not to have to know that - my brain is full ;-)
gd_on:
--- Code: ---How do I restore to get the Code::blocks tab in Logs and Others?
--- End code ---
In "logs & other", right clic on a tab, then choose "Toggle..." to restore the masked tabs
gd_on
pabristow:
After restoring the Code::blocks tab (thanks for info on this - I have much to learn :( ).
s expected
Code::Blocks window contains
Rebuild project:4
test
test
and if I paste the full command given into the post_build box (leaving the [[test]] command in the pre-build box).
It now asks for permission (which I gave for all future uses of the script) and the Code::blocks window now contains
Rebuild project:4
test
and the Build log is as before
--- Code: ----------------- Clean: Debug_clang900 in hello_exceptions (compiler: LLVM Clang 900 Compiler)---------------
Cleaned "hello_exceptions - Debug_clang900"
Running target pre-build steps
-------------- Build: Debug_clang900 in hello_exceptions (compiler: LLVM Clang 900 Compiler)---------------
clang++.exe -g --verbose -c I:\Cpp\hello_boost\hello_exceptions\hello_exceptions.cpp -o obj\Debug\hello_exceptions.o
clang++.exe -o bin\Debug\hello_exceptions.exe obj\Debug\hello_exceptions.o
clang version 9.0.0 (tags/RELEASE_900/final)
Target: x86_64-pc-windows-msvc
Thread model: posix
InstalledDir: C:\LLVM\clang-900\LLVM\bin
"C:\\LLVM\\clang-900\\LLVM\\bin\\clang++.exe" -cc1 -triple x86_64-pc-windows-msvc19.24.28207 -emit-obj -mrelax-all -mincremental-linker-compatible -disable-free -disable-llvm-verifier -discard-value-names -main-file-name hello_exceptions.cpp -mrelocation-model pic -pic-level 2 -mthread-model posix -fmath-errno -masm-verbose -mconstructor-aliases -munwind-tables -target-cpu x86-64 -gcodeview -debug-info-kind=limited -momit-leaf-frame-pointer -v -coverage-notes-file "I:\\Cpp\\hello_boost\\hello_exceptions\\obj\\Debug\\hello_exceptions.gcno" -resource-dir "C:\\LLVM\\clang-900\\LLVM\\lib\\clang\\9.0.0" -internal-isystem "C:\\LLVM\\clang-900\\LLVM\\lib\\clang\\9.0.0\\include" -internal-isystem "C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Preview\\VC\\Tools\\MSVC\\14.24.28207\\include" -internal-isystem "C:\\Program Files (x86)\\Windows Kits\\10\\Include\\10.0.18362.0\\ucrt" -internal-isystem "C:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.18362.0\\shared" -internal-isystem "C:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.18362.0\\um" -internal-isystem "C:\\Program Files (x86)\\Windows Kits\\10\\include\\10.0.18362.0\\winrt" -fdeprecated-macro -fdebug-compilation-dir "I:\\Cpp\\hello_boost\\hello_exceptions" -ferror-limit 19 -fmessage-length 0 -fno-use-cxa-atexit -fms-extensions -fms-compatibility -fms-compatibility-version=19.24.28207 -std=c++14 -fdelayed-template-parsing -fobjc-runtime=gcc -fcxx-exceptions -fexceptions -fdiagnostics-show-option -faddrsig -o "obj\\Debug\\hello_exceptions.o" -x c++ "I:\\Cpp\\hello_boost\\hello_exceptions\\hello_exceptions.cpp"
clang -cc1 version 9.0.0 based upon LLVM 9.0.0 default target x86_64-pc-windows-msvc
#include "..." search starts here:
#include <...> search starts here:
C:\LLVM\clang-900\LLVM\lib\clang\9.0.0\include
C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\VC\Tools\MSVC\14.24.28207\include
C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\ucrt
C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\shared
C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\um
C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\winrt
End of search list.
Output file is bin\Debug\hello_exceptions.exe with size 231.00 KB
Running target post-build steps
Nothing to be done (all items are up-to-date).
--- End code ---
Is the script line not quite right yet?
BlueHazzard:
Do you have a new file beside the log file? You should not see anything in the log output, but there should be a new log file, called like the compiler beside the old html log file.
If you want to know how the file is called, paste the following in the post build steps and look in the log
--- Quote ---[[Log(_("$(PROJECTNAME)_build_log_") + GetProjectManager().GetActiveProject().GetCurrentlyCompilingTarget().GetTitle() + _("_") + GetProjectManager().GetActiveProject().GetCurrentlyCompilingTarget().GetCompilerID() + _(".html"))]]
--- End quote ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version