User forums > Nightly builds

The 17 June 2012 build (8059) is out.

<< < (10/11) > >>

gd_on:
Hi,
there is apparently a small error introduced at line 71 in sdk/autodetectcompilers.cpp (svn 8086) which makes xgettext fail to prepare strings for CB Translation. It's a non ascii character following the word *probably*.
Its :

--- Code: ---            else // The compiler is *probably*Ü invalid, but at least a master-path is set
--- End code ---
I suppose the good line should be :

--- Code: ---            else // The compiler is *probably* invalid, but at least a master-path is set
--- End code ---

gd_on

MortenMacFly:

--- Quote from: gd_on on July 07, 2012, 04:13:27 pm ---there is apparently a small error introduced at line 71 in sdk/autodetectcompilers.cpp (svn 8086) which makes xgettext fail to prepare strings for CB Translation.

--- End quote ---
My fault. Fixed in SVN.

stahta01:
Noticed a warning in the wxSmith build; no idea how long it has been there.
I am using MinGW GCC version 4.6.x and 4.7.0 doing testing to see how they work.
It might be a new warning with one of those versions.

Tim S.


--- Code: ---src\plugins\contrib\wxSmith\wxwidgets\wxsitemresdataobject.cpp|127|warning: converting 'false' to pointer type 'wxsItem*' [-Wconversion-null]|

--- End code ---

Patch untested for working; compiled on Windows OK


--- Code: ---Index: src/plugins/contrib/wxSmith/wxwidgets/wxsitemresdataobject.cpp
===================================================================
--- src/plugins/contrib/wxSmith/wxwidgets/wxsitemresdataobject.cpp (revision 8093)
+++ src/plugins/contrib/wxSmith/wxwidgets/wxsitemresdataobject.cpp (working copy)
@@ -124,7 +124,7 @@
  if ( !Item )
  {
         Item = wxsItemFactory::Build(_T("Custom"),Data);
-        if ( !Item ) return false;
+        if ( !Item ) return 0;
  }
 
  Item->XmlRead(Root,true,true);

--- End code ---

Tim S.

Epicurus:
Thanks again for your help MortenMacFly! I installed MinGW and my ProjectEuler exercise compiled and ran beautifully!

Do I need to worry about adding the directory for MinGW every time I upgrade the nightly? Presumably, I would delete my old version and install the new version in the same directory, including the two necessary DLLs.

MortenMacFly:

--- Quote from: Epicurus on July 09, 2012, 06:31:49 am ---Do I need to worry about adding the directory for MinGW every time I upgrade the nightly?

--- End quote ---
Usually not. The path is stored in the default.conf configuration file of Code::BLocks which is by default not in the installation folder. However, if you are using a portable installation - then it is. If you remove it, you have to setup the path again afterwards.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version