User forums > Nightly builds
The 11 May 2006 build is out.
takeshimiya:
--- Quote from: Zingam on May 12, 2006, 10:04:59 am ---I think the DDE bug is back. Well not in the same way but still there is something when the pop-up pops up to ask to select a compiler.
--- End quote ---
No, that's not the DDE bug, it's another "bug" (it's not really a bug): when a compiler get's added to C::B (the other day support for the MSVC2005 was added), the autodetection of compilers dialog appears once again, one time.
--- Quote from: Zingam on May 12, 2006, 10:04:59 am ---BTW will you someday make it possible for DMD compiler to compile debugging info?
--- End quote ---
What are the necesary flags to do so, and what fails currently?
Escorter:
--- Quote from: nfz on May 12, 2006, 01:43:13 am ---So maybe it is an environment issue. What is your OS, are you using unicode or ansi build of WxWidgets, etc?
--- End quote ---
OS: WinXP Pro
WxWidgets: Unicode
--- Quote from: mandrav on May 12, 2006, 08:34:57 am ---There should be a codeblocks.rpt file containing the crash dump. Can you zip it and post it?
--- End quote ---
http://rapidshare.de/files/20283719/codeblocks.7z.html
Zingam:
--- Quote from: Takeshi Miya on May 12, 2006, 10:12:40 am ---
--- Quote from: Zingam on May 12, 2006, 10:04:59 am ---I think the DDE bug is back. Well not in the same way but still there is something when the pop-up pops up to ask to select a compiler.
--- End quote ---
No, that's not the DDE bug, it's another "bug" (it's not really a bug): when a compiler get's added to C::B (the other day support for the MSVC2005 was added), the autodetection of compilers dialog appears once again, one time.
--- End quote ---
What happened is: I unpacked CB in the directory where the previous version was installed. I double clicked a .cpp file and the dialog to select a compiler appeared and also an error message that the file could not be found and it wasn't opened after CB was loaded.
--- Quote ---
--- Quote from: Zingam on May 12, 2006, 10:04:59 am ---BTW will you someday make it possible for DMD compiler to compile debugging info?
--- End quote ---
What are the necesary flags to do so, and what fails currently?
--- End quote ---
http://forums.codeblocks.org/index.php?action=post;quote=24511;topic=3087.0;sesc=b30e74af010293a1e1f46ce18869e63b
When normally files are compiled with th DMD compiler they are added like this: DMD file1.d file2.d file3.d etc. and then they are linked but CB compiles them individually DMD file1.d DMD file2.d and then they are linked in such way no debuging info is added because it seems the -g switch does not work. There is a way to pass an option to the linker: /CO but I cannot find a way to make CB pass it to the linker.
To pass a switch to the linker, we use the compiler switch -L like this dmd main.d -L/CO
Michael:
--- Quote from: Zingam on May 13, 2006, 08:42:53 pm ---
--- Quote from: Takeshi Miya on May 12, 2006, 10:12:40 am ---
--- Quote from: Zingam on May 12, 2006, 10:04:59 am ---I think the DDE bug is back. Well not in the same way but still there is something when the pop-up pops up to ask to select a compiler.
--- End quote ---
No, that's not the DDE bug, it's another "bug" (it's not really a bug): when a compiler get's added to C::B (the other day support for the MSVC2005 was added), the autodetection of compilers dialog appears once again, one time.
--- End quote ---
What happened is: I unpacked CB in the directory where the previous version was installed. I double clicked a .cpp file and the dialog to select a compiler appeared and also an error message that the file could not be found and it wasn't opened after CB was loaded.
--- End quote ---
I will never do so. IMHO, it is better (and to avoid potential problems) to not unpack a C::B rev on the directory of a previous one.
Best wishes,
Michael
Zingam:
I delete "shared" always and there were never problems with that.
Navigation
[0] Message Index
[*] Previous page
Go to full version