Code::Blocks

User forums => Nightly builds => Topic started by: killerbot on October 23, 2012, 09:43:17 pm

Title: The 23 October 2012 build (8476) is out.
Post by: killerbot on October 23, 2012, 09:43:17 pm
Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

Before you use a nightly make sure you understand how it works (http://forums.codeblocks.org/index.php/topic,3232.0.html).

A link to the unicode windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw28u_gcc_cb_wx2812_gcc452-TDM.7z

For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://prdownload.berlios.de/codeblocks/mingwm10_gcc452-TDM.7z

The 23 October 2012 build is out.
  - Windows :
   http://prdownload.berlios.de/codeblocks/CB_20121023_rev8476_win32.7z
  - Linux :
   none

Resolved Fixed:


Regressions/Confirmed/Annoying/Common bugs:


Title: Re: The 23 October 2012 build (8476) is out.
Post by: KirkD on October 24, 2012, 06:55:10 pm
Unzipping over build 8438 I get an error stating that the compiler plugin could not be loaded.  Same problem with the most previous build, rev8466.  Rev8438 is the last version that works.

Title: Re: The 23 October 2012 build (8476) is out.
Post by: oBFusCATed on October 24, 2012, 07:05:01 pm
Unzipping over build 8438...
This operation begs for problems, please use a clean directory.
Title: Re: The 23 October 2012 build (8476) is out.
Post by: KirkD on October 24, 2012, 07:06:54 pm
Done.  What I found was that the 7-zip file defaulted to using no pathnames whereas previous versions defaulted to using stored pathnames.  Not sure why the difference.  A clean directory and switching to using saved pathnames solved the problem.

BTW, if unzipping over a previous nightly is a problem, it might be useful to say this on the How to Use a Nightly Build page in this forum.  Specifically, it currently says:

5. Upgrading the nightly
If you followed the advised approach your compilers, debuggers are separated from CB itself. This means you can delete your CB nightly install directory without any harm, since your user settings are stored in your user profile directory (eg. default.conf), and unzip the new nightly build, or you can unzip your new nightly build on top of your previous nightly build. In the latter case be sure to overwrite all files !!!

Title: Re: The 23 October 2012 build (8476) is out.
Post by: MortenMacFly on October 24, 2012, 08:22:13 pm
BTW, if unzipping over a previous nightly is a problem, it might be useful to say this on the How to Use a Nightly Build page in this forum.  Specifically, it currently says:
[...]
In the latter case be sure to overwrite all files !!!
The sentence is correct, if you carefully follow the advise.
If files are left that are not overwritten (except the config for a portable install), this will lead to issues.
Title: Re: The 23 October 2012 build (8476) is out.
Post by: oBFusCATed on October 24, 2012, 09:52:45 pm
If you ask me I'll remove this sentence to prevent user confusion and as an excuse :)
Title: Re: The 23 October 2012 build (8476) is out.
Post by: KirkD on October 24, 2012, 10:04:47 pm
Of course I would overwrite all the files, but I guess that isn't assumed here.  It seems a bit uncertain based on the discussion.
Title: Re: The 23 October 2012 build (8476) is out.
Post by: MortenMacFly on October 25, 2012, 06:54:40 am
If you ask me I'll remove this sentence to prevent user confusion and as an excuse :)
...killerbot?

Maybe better would be something like:
"Remove everything except default.conf / *.conf (if it exists in the installation directory) and unzip into that folder."
Title: Re: The 23 October 2012 build (8476) is out.
Post by: killerbot on October 25, 2012, 07:40:11 am
I will rephrase, that it is best to always delete the previous one, and no longer talk about overwriting.

The text also suggests that the user settings are kept in a different location (which is the default behavior), I would not talk about potentially having those files in the nightly installation directory, in order to keep those in that case. Sounds to confusing to me.

Question though : what will happen/should to the new compiler settings for the xml compiler .... ?
Title: Re: The 23 October 2012 build (8476) is out.
Post by: MortenMacFly on October 25, 2012, 08:50:43 am
Question though : what will happen/should to the new compiler settings for the xml compiler .... ?
The base compiler settings are stored inside the installation folder. All new settings (i.e. if you have added new compiler flags) are stored in the user-settings directory. Basically the same as with plugins/scripts meaning that there is no portable way to my knowledge... I might be wrong. However, for a new nightly installation there is no problem.
Title: Re: The 23 October 2012 build (8476) is out.
Post by: White-Tiger on October 25, 2012, 03:26:46 pm
I will rephrase, that it is best to always delete the previous one, and no longer talk about overwriting.
[...]
well.... u've got me now^^ What is the damn problem with that? I'll always overwrite... and I will never ever delete them (ok actually... my script does that already from the very beginning^^)
Does the problem only reside inside the "share" folder cuz there r all the plugins? And thus there might be a renamed or even deleted one left, which then kills C::B?

Currently I'll compile C::B myself because I've made some for me important changes (and because I want to use mingw-builds instead of TDM as mingw-builds is always up-to-date) and because of that, I've written a batch file that copies C::B to my "install" location... it basically deletes the "share" folder + all .exe/.dll except my "wxmsw28u_gcc_custom.dll"
So it is a "clean install" already...
I would only suggest ppl to delete the "share" folder and overwrite everything else. Unused DLLs left shouldn't make a problem... only left out-dated plugins. You could even add a "clean.cmd" file to the nightly so that ppl execute that file before copying^^
Title: Re: The 23 October 2012 build (8476) is out.
Post by: jens on October 25, 2012, 04:23:52 pm
As usual:
Debian packages (binaries and sources) for 32-bit and 64-bit systems can be found in my debian-repo (http://apt.jenslody.de/).
Fedora packages (binaries and sources) for 32-bit and 64-bit systems (fc16, fc17 and fc18) can be found in my rpm-repo (http://rpm.jenslody.de) .
Title: Re: The 23 October 2012 build (8476) is out.
Post by: MortenMacFly on October 26, 2012, 06:27:22 am
Does the problem only reside inside the "share" folder cuz there r all the plugins? And thus there might be a renamed or even deleted one left, which then kills C::B?
Some examples:

So yes: If you are certain what you do its safe to overwrite, but its definitely way more save to delete the folder before, especially if you have no idea about such stuff.

We want to go the fail-safe way here to avoid trouble in the beginning. Thus the explanation as it is.
Title: Re: The 23 October 2012 build (8476) is out.
Post by: carra on October 27, 2012, 10:55:05 am
This nightly still has the bug of inserting extra lines in abbreviations. It was described by hongwenjun for 4866, here: http://forums.codeblocks.org/index.php/topic,16983.msg115763.html#msg115763

I can't work with this at all since I make heavy use of abbreviations, so I will have to revert to previous versions for now  :(
Title: Re: The 23 October 2012 build (8476) is out.
Post by: MortenMacFly on October 27, 2012, 05:20:58 pm
I can't work with this at all since I make heavy use of abbreviations, so I will have to revert to previous versions for now  :(
We will take care... (maybe its already resolved in SVN...)
Title: Re: The 23 October 2012 build (8476) is out.
Post by: stefanos_ on October 27, 2012, 09:59:26 pm
Can someone see this old issue http://forums.codeblocks.org/index.php/topic,16560.msg112659.html#msg112659 (http://forums.codeblocks.org/index.php/topic,16560.msg112659.html#msg112659) :/ ? It's still there and I cannot work like this. The hint is really annoying like that!

Version: svn-8477 (self-compiled as always)
OS: GNU / Linux Debian wheezy (32-bit)
Compiler: GCC-4.6
Title: Re: The 23 October 2012 build (8476) is out.
Post by: carra on October 27, 2012, 10:41:39 pm
We will take care... (maybe its already resolved in SVN...)
Glad to hear that Morten :)
Title: Re: The 23 October 2012 build (8476) is out.
Post by: MortenMacFly on October 27, 2012, 10:49:19 pm
Glad to hear that Morten :)
Well I just tried and I cannot reproduce. There has been a patch applied recently - if you are willing, try with t self-compiled version from trunk (to wait for the next nightly). Nag me again if it isn't resolved.

Maybe in between state again exactly what to do to reproduce, including:
- version of C::B
- platform
- editor settings
- abbreviations
- steps you do to achieve the unwanted result.

BTW: Are you sure your abbreviations are setup correctly? I.e. are the line feeds OK there, too?
Title: Re: The 23 October 2012 build (8476) is out.
Post by: Alpha on October 28, 2012, 02:56:40 am
This nightly still has the bug of inserting extra lines in abbreviations.
It looks like I made one to many assumptions in optimizing the patch for revision 8434 (http://svn.berlios.de/wsvn/codeblocks/?op=revision&rev=8434&peg=8484).
Well I just tried and I cannot reproduce.
This behavior will only occur during use of a custom abbreviation, and only if it was created with CR LF line endings.

The "correct" solution is probably to simply save in the format expected for input:
Code: [Select]
Index: src/plugins/abbreviations/abbreviations.cpp
===================================================================
--- src/plugins/abbreviations/abbreviations.cpp (revision 8478)
+++ src/plugins/abbreviations/abbreviations.cpp (working copy)
@@ -279,7 +279,6 @@
             continue;
         // convert non-printable chars to printable
         code.Replace(_T("\\n"), _T("\n"));
-        code.Replace(_T("\\r"), _T("\r"));
         code.Replace(_T("\\t"), _T("\t"));
         m_AutoCompleteMap[name] = code;
     }
@@ -349,8 +348,9 @@
     {
         wxString code = it->second;
         // convert non-printable chars to printable
+        code.Replace(_T("\r\n"), _T("\\n"));
         code.Replace(_T("\n"), _T("\\n"));
-        code.Replace(_T("\r"), _T("\\r"));
+        code.Replace(_T("\r"), _T("\\n"));
         code.Replace(_T("\t"), _T("\\t"));
 
         ++count;

However, settings would still create problems if not converted:
Code: [Select]
Index: src/plugins/abbreviations/abbreviations.cpp
===================================================================
--- src/plugins/abbreviations/abbreviations.cpp (revision 8478)
+++ src/plugins/abbreviations/abbreviations.cpp (working copy)
@@ -279,8 +279,11 @@
             continue;
         // convert non-printable chars to printable
         code.Replace(_T("\\n"), _T("\n"));
-        code.Replace(_T("\\r"), _T("\r"));
+        code.Replace(_T("\\r"), _T("\r")); // should not exist ...
         code.Replace(_T("\\t"), _T("\t"));
+        // ... but remove if it does (EOL style is matched just before code generation)
+        code.Replace(_T("\r\n"), _T("\n"));
+        code.Replace(_T("\r"), _T("\n"));
         m_AutoCompleteMap[name] = code;
     }
 
@@ -349,8 +352,9 @@
     {
         wxString code = it->second;
         // convert non-printable chars to printable
+        code.Replace(_T("\r\n"), _T("\\n"));
         code.Replace(_T("\n"), _T("\\n"));
-        code.Replace(_T("\r"), _T("\\r"));
+        code.Replace(_T("\r"), _T("\\n"));
         code.Replace(_T("\t"), _T("\\t"));
 
         ++count;
Title: Re: The 23 October 2012 build (8476) is out.
Post by: carra on October 28, 2012, 01:20:16 pm
This behavior will only occur during use of a custom abbreviation, and only if it was created with CR LF line endings.
Yes, this makes sense: I'm under Windows and my abbreviations are custom  :D
Title: Re: The 23 October 2012 build (8476) is out.
Post by: MortenMacFly on October 28, 2012, 02:45:14 pm
The "correct" solution is probably to simply save in the format expected for input:
This sounds reasonable and also explains why I was unable to reproduce. I've applied that one. Thanks! :-)
Title: Re: The 23 October 2012 build (8476) is out.
Post by: MortenMacFly on October 28, 2012, 02:46:17 pm
Yes, this makes sense: I'm under Windows and my abbreviations are custom  :D
The next nightly (not the one of today) is worth a try for you... or you self-compile is from trunk now.
Title: Re: The 23 October 2012 build (8476) is out.
Post by: Alpha on October 28, 2012, 04:48:07 pm
I've applied that one.
It looks like application might have been partial?  Literal "\\r" strings from previous saves must be removed.
Code: [Select]
Index: src/plugins/abbreviations/abbreviations.cpp
===================================================================
--- src/plugins/abbreviations/abbreviations.cpp (revision 8485)
+++ src/plugins/abbreviations/abbreviations.cpp (working copy)
@@ -278,11 +278,11 @@
         if (name.IsEmpty())
             continue;
         // convert non-printable chars to printable
-        code.Replace(_T("\\n"),  _T("\n"));
-        code.Replace(_T("\\t"),  _T("\t"));
-        // ... but remove if it does (EOL style is matched just before code generation)
-        code.Replace(_T("\r\n"), _T("\n"));
-        code.Replace(_T("\r"),   _T("\n"));
+        code.Replace(_T("\\n"),   _T("\n"));
+        code.Replace(_T("\\t"),   _T("\t"));
+        // should not exist, but remove if it does (EOL style is matched just before code generation)
+        code.Replace(_T("\\r\n"), _T("\n"));
+        code.Replace(_T("\\r"),   _T("\n"));
         m_AutoCompleteMap[name] = code;
     }
 
@@ -351,9 +351,9 @@
     {
         wxString code = it->second;
         // convert non-printable chars to printable
-        code.Replace(_T("\r\n"), _T("\\n"));
+        code.Replace(_T("\r\n"), _T("\\n")); // EOL style will be matched just before code generation
         code.Replace(_T("\n"),   _T("\\n"));
-        code.Replace(_T("\r"),   _T("\\n")); // should not exist ...
+        code.Replace(_T("\r"),   _T("\\n"));
         code.Replace(_T("\t"),   _T("\\t"));
 
         ++count;
Title: Re: The 23 October 2012 build (8476) is out.
Post by: oBFusCATed on October 29, 2012, 07:24:57 pm
If you ask me the best solution is to always save it in \n or \n\r mode and apply the proper mode when displaying, applying the abbreviation.
Title: Re: The 23 October 2012 build (8476) is out.
Post by: Alpha on October 29, 2012, 09:16:12 pm
If you ask me the best solution is to always save it in \n or \n\r mode and apply the proper mode when displaying, applying the abbreviation.
Um... if I understand you correctly, I think that is exactly what I did?
Title: Re: The 23 October 2012 build (8476) is out.
Post by: oBFusCATed on October 29, 2012, 09:35:26 pm
This is good :)