User forums > Nightly builds
The 06 December 2014 build (10050) is out.
Jenna:
--- Quote from: Melchior on January 09, 2015, 02:24:42 am ---I have attached a copy of the update_debug.bat can you guys please get it committed?
--- End quote ---
This will for sure not be committed, because it does not make sense.
The build-process (and update[.bat]-script) create two folders: devel and output.
The first one is (as the name clearly states) for developping and includes debugging symbols, the second one includes the stripped (release-)version.
I don't see any cause to change this.
Renaming the *.bat-files to *.cmd is possible, but has no real benefit (at least not at this moment), but might break existing (more or less aoutomated) build-processes, that rely on the existing names.
Melchior:
I attached a png image where I combined the image of all three Global Variables needed by
Code-blocks....
- Boost
- cb_release_type
- wx
yah I get the "quote" thing... CodeBlocks treats the whole box as a string so " " is unnecessary and
only used here to show a bit of text as a string...
"F:\Dev-src\CodeBlocks_src\src -g"
is what I am using now after your suggestion to add to base and mot a user-defined variable....
I also attached the rpt file I found, thx for letting me know about it =D...
debugging plugin? I didn't see one on the plugin drop down, you must mean the main debug drop down menu..
For most debugging I create a simple cmd file like this one which I created to run codeblocks.exe through gdb...
Debugging (gdb)_CodeBlocks.cmd
--- Quote ---@ECHO on
:: Core Dump Checking through the GNU Debugger (GDB)
::
:: Symbol Servers
:: - http://msdl.microsoft.com/download/symbols
::
:: --directory=" " // Specifies location of Source code,
:: // multiply Directories can be listed one per cmd flag.
::
:: --symbols=" " // Debug Symbol file(s).
:: --exec=" " // exe to be debugged (does not contain debug symbols).
:: --se=" " // exe to be debugged (contains debug symbols ^_^).
gdb -readnow -se="codeblocks.exe"
pause
--- End quote ---
for the .bat to .cmd suggestion, fair enough.
--- Quote from: jens on January 09, 2015, 06:21:50 am ---
--- Quote from: Melchior on January 09, 2015, 02:24:42 am ---I have attached a copy of the update_debug.bat can you guys please get it committed?
--- End quote ---
This will for sure not be committed, because it does not make sense.
The build-process (and update[.bat]-script) create two folders: devel and output.
The first one is (as the name clearly states) for developping and includes debugging symbols, the second one includes the stripped (release-)version.
I don't see any cause to change this.
Renaming the *.bat-files to *.cmd is possible, but has no real benefit (at least not at this moment), but might break existing (more or less automated) build-processes, that rely on the existing names.
--- End quote ---
I believe you misunderstand me....
there exists now in the repo three update.bat files, and all three are release grade:
- update.bat <-- wx v2.8
- update30.bat <-- wx v3.0
- update30_64.bat <-- wx v3.0 but it appears to be 64bit..
all three files already part of the Codeblocks svn repository have strip at the end of them...
--- Quote ---echo Stripping debug info from output tree
strip output30_64\*.exe
strip output30_64\*.dll
strip %CB_OUTPUT_RESDIR%\plugins\*.dll
--- End quote ---
so I made a copy of the "update.bat" file and renamed it "update_debug.bat"
where I commented out the strip commands so debugging info remains intact
my customized copy of "update.bat" is not part of the repository and I was asking for it to be added
That and maybe a bit of renaming work... =D
As these two files imply they are for wxWidgets v3.0
- update30.bat
- update30_64.bat
would it not make sense to rename
update.bat and update_debug.bat
to
- update28.bat
- update28_debug.bat
? optional suggestion of course...
[attachment deleted by admin]
Jenna:
--- Quote from: Melchior on January 09, 2015, 07:46:41 am ---
--- Quote from: jens on January 09, 2015, 06:21:50 am ---
--- Quote from: Melchior on January 09, 2015, 02:24:42 am ---I have attached a copy of the update_debug.bat can you guys please get it committed?
--- End quote ---
This will for sure not be committed, because it does not make sense.
The build-process (and update[.bat]-script) create two folders: devel and output.
The first one is (as the name clearly states) for developing and includes debugging symbols, the second one includes the stripped (release-)version.
I don't see any cause to change this.
Renaming the *.bat-files to *.cmd is possible, but has no real benefit (at least not at this moment), but might break existing (more or less automated) build-processes, that rely on the existing names.
--- End quote ---
I believe you misunderstand me....
--- End quote ---
I think it's not me who misunderstands something.
It's your choice how to debug C::B, but I prefer to use C::B to do it and never had unsolvable problems.
Using gdb via commandline is possible and makes sense sometimes, but most of the times a gui is much easier to use.
Aleksandr:
The height of the Todo list docked to the top or bottom is not remembered after hiding and is reset to the some minimum in the subsequent show.
BTW, there is some possibility to make the Todo list as a tab in the Logs & others?
ollydbg:
--- Quote from: eMan.Lived on January 10, 2015, 02:15:53 am ---BTW, there is some possibility to make the Todo list as a tab in the Logs & others?
--- End quote ---
Yes, you can check on the option: Menu->Settings->Environment->TO DO->Include the todo list in the message panel, and restart C::B.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version