Author Topic: The 02 August 2014 build (9854) is out.  (Read 16928 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5164
The 02 August 2014 build (9854) is out.
« on: August 02, 2014, 10:52:00 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.

A link to the unicode windows wxWidget dll for Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/wxmsw28u_gcc_cb_wx2812_gcc481-TDM.7z

For those who might need this one (when no MingW installed on your system) : the mingw10m.dll : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/mingwm10_gcc481-TDM.7z

The 02 August 2014 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2014/CB_20140802_rev9854_win32.7z
  - Linux :
   none

Resolved Fixed:

  • compiler: resolve bug 19021, new compiler flags created from the per-project settings dlg are not saved to running memory
    See http://forums.codeblocks.org/index.php/topic,18019.0.html
  • CC: apply patch by Huki. In DoParse(), when parsing "else" we try to eat the arguments. It breaks support for "else-if" (we will end up eating the "if"), and anyway there is no need to skip anything after "else". See details in http://forums.codeblocks.org/index.php/topic,18315.msg132594.html#msg132594.
  • CC: apply patch by Huki. Don't skip successive opening or closing brackets, see details in http://forums.codeblocks.org/index.php/topic,18315.msg132594.html#msg132594.
  • CC: remove the last parameter of Parser::Parse() function. It was the LoaderBase pointer, but this argument is always set as nullptr, otherwise, it will report a memory leak problem. The loader must be allocated in the Parse() function, and later deleted in ParserThread::InitTokenizer() function.
  • make the menu entries normal items (were check items which was wrong)
  • SmartIndentHDL: do correctly unindent "end function" and "end procedure".
  • compiler: add support for the soft CPUs lm32, lm8 and zpu
  • compiler: rate limit build message column auto fit frequency to reduce excessive overhead when builds produce thousands of messages
  • CC: call SmartIndentPlugin->OnCCDone() when CC is done
  • SmartIndentHDL: tidy up formating when CC finished

Regressions/Confirmed/Annoying/Common bugs:


    « Last Edit: August 03, 2014, 09:08:06 am by killerbot »

    Offline killerbot

    • Administrator
    • Lives here!
    • *****
    • Posts: 5164
    Re: The 02 August 2014 build (9854) is out.
    « Reply #1 on: August 02, 2014, 11:05:43 pm »
    be patient, there were upload issues .... Fixed.
    « Last Edit: August 03, 2014, 09:08:38 am by killerbot »

    ToApolytoXaos

    • Guest
    Re: The 02 August 2014 build (9854) is out.
    « Reply #2 on: August 03, 2014, 08:54:04 am »
    The parser issue with header files still exists; if you create a new header file and try to include any header file, it won't suggest anything at all, neither header file names nor C++ keyword tags; only the current header's name.

    Offline jens

    • Administrator
    • Lives here!
    • *****
    • Posts: 7265
      • Jens' unofficial debian-repository for the Code::Blocks - IDE
    Re: The 02 August 2014 build (9854) is out.
    « Reply #3 on: August 03, 2014, 10:52:02 am »
    As usual:

    Debian packages (binaries and sources) for 32-bit and 64-bit systems can be found in my debian-repo.
    Fedora packages (binaries and sources) for 32-bit and 64-bit systems (fc19, fc20 and rawhide) and RedHat/CentOS 5 and 6 packages (also 32-bit and 64-bit) can be found in my rpm-repo .

    Offline shurick

    • Multiple posting newcomer
    • *
    • Posts: 35
    Re: The 02 August 2014 build (9854) is out.
    « Reply #4 on: August 03, 2014, 01:03:41 pm »
    Packages for openSUSE (binaries and sources) for 32-bit and 64-bit.
    Packages for openSUSE http://codeblocks.esy.es  (binaries and sources) for 32-bit and 64-bit.

    Offline cacb

    • Regular
    • ***
    • Posts: 389
    Re: The 02 August 2014 build (9854) is out.
    « Reply #5 on: August 05, 2014, 09:46:00 am »
    Thanks for your work releasing nightlies.

    I have just installed 9854 on Windows 7 and I am experiencing a problem that was not there before (i.e. I was using 9660)

    My projects all have 4 build targets, 2 MSVC targets for use on Windows and 2 GCC targets for use on Linux. Some of these projects use wxWidgets, and therefore also wx-config. But wx-config on windows (wx-config-win) is really a different animal than wx-config on linux, using rather different options.

    On both Windows and Linux I have defined a 'wx' global variable, and using it

    Windows
                <Compiler>
                   <Add option="/MD" />
                   <Add option="/GF" />
                   <Add option="/Ox" />
                   <Add option="/W3" />
                   <Add option="/EHsc" />
                   <Add option="`$(CPDE_USR)\bin\wx-config.exe --prefix=$(#wx) --wxcfg=$(#wx.release) --cxxflags`" />
                   <Add option="/D_CRT_SECURE_NO_WARNINGS" />
                   <Add option="/D_CRT_NONSTDC_NO_DEPRECATE" />
                   <Add option="/D_CRT_SECURE_DEPRECATE" />
                </Compiler>


    Linux

                <Compiler>
                   <Add option="-std=c++0x" />
                   <Add option="-W" />
                   <Add option="-fPIC" />
                   <Add option="-DNOPCH" />
                   <Add option="-fexceptions" />
                   <Add option="-D_DEBUG" />
                   <Add option="-g" />
                   <Add option="`$(#wx.config) --cxxflags --debug`" />
                </Compiler>


    As you can see, there are different user defined fields for global variable 'wx' depending on which compiler is being used. The ".config" field is not used under Windows/MSVC for example.

    However, when I now start CB 9854 with a MSVC compiler as default and open a C::B project, I now get "yellow boxes" popping up, complaining about missing global variable member definitions that are never going to be needed on this platform. This was never an issue before.

    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 11821
      • Travis build status
    Re: The 02 August 2014 build (9854) is out.
    « Reply #6 on: August 05, 2014, 10:33:14 am »
    This was never an issue before.
    C::B is more vocal about invalid global variables now, so just put something to silence it and you're good to go.
    (most of the time I ignore long posts)
    [strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

    Offline cacb

    • Regular
    • ***
    • Posts: 389
    Re: The 02 August 2014 build (9854) is out.
    « Reply #7 on: August 05, 2014, 04:33:05 pm »
    C::B is more vocal about invalid global variables now, so just put something to silence it and you're good to go.

    Ok, seems to work on Windows. Thanks.

    ToApolytoXaos

    • Guest
    Re: The 02 August 2014 build (9854) is out.
    « Reply #8 on: August 05, 2014, 11:43:27 pm »
    The parser issue with header files still exists; if you create a new header file and try to include any header file, it won't suggest anything at all, neither header file names nor C++ keyword tags; only the current header's name.

    I have just tested the same proceduce on Windows XP (VirtualBox) and it works just fine; the issue insists on GNU / Linux. By the way, on Windows it behaves so nice, so smoothly, and so freaking fast, let alone accurate results!

    Well done, team!

    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 11821
      • Travis build status
    Re: The 02 August 2014 build (9854) is out.
    « Reply #9 on: August 06, 2014, 12:40:53 am »
    Are you doing the 100% exact steps to reproduce the problem? Can you post them?
    (most of the time I ignore long posts)
    [strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

    ToApolytoXaos

    • Guest
    Re: The 02 August 2014 build (9854) is out.
    « Reply #10 on: August 06, 2014, 03:00:48 pm »
    Yes of course.

    • Click on "Create new project" from Code::Blocks
    • click on "Empty Project"
    • press Ctrl+Shift+N to create a new file; name it anything with .h as your file extension
    • use Ctrl+J to choose guard; enter the macro preprocessing name for your header file
    • start typing an include header file name and see if it works; for me it displays only my header's name and nothing else.

    Offline jens

    • Administrator
    • Lives here!
    • *****
    • Posts: 7265
      • Jens' unofficial debian-repository for the Code::Blocks - IDE
    Re: The 02 August 2014 build (9854) is out.
    « Reply #11 on: August 07, 2014, 07:18:16 am »
    Yes of course.

    • Click on "Create new project" from Code::Blocks
    • click on "Empty Project"
    • press Ctrl+Shift+N to create a new file; name it anything with .h as your file extension
    • use Ctrl+J to choose guard; enter the macro preprocessing name for your header file
    • start typing an include header file name and see if it works; for me it displays only my header's name and nothing else.

    Seems to work correctly on my Fedora 20 system with newest nightly from my repo.
    At least it shows me tons of (systemwide installed) headers.

    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 11821
      • Travis build status
    Re: The 02 August 2014 build (9854) is out.
    « Reply #12 on: August 07, 2014, 09:39:31 am »
    Works here, too - Latest Gentoo (rev9853).
    (most of the time I ignore long posts)
    [strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

    ToApolytoXaos

    • Guest
    Re: The 02 August 2014 build (9854) is out.
    « Reply #13 on: August 07, 2014, 07:15:03 pm »
    Okay, I decided to double check it. I opened an existing project and added an existing header file created outside project and this way it works fine. If I create though a new project and repeat the steps I have aforementioned for a newly created header file, it won't work.

    Is there any kind of setting I should check anywhere?

    UPDATE: I have found a way which works and IMHO indicates a bug in parser's mechanism. Right after #include, a space follows and then you should use either angle brackets or double quotes for local header files; before you enter the opening angle bracket, press space bar and parser delays 2-3 seconds and calls all of header files. Now it works no matter what you do.
    « Last Edit: August 07, 2014, 07:24:51 pm by ToApolytoXaos »

    Offline damorin

    • Multiple posting newcomer
    • *
    • Posts: 40
    Re: The 02 August 2014 build (9854) is out.
    « Reply #14 on: August 15, 2014, 09:09:11 pm »
    Hi,

    I was editing a quite large file and there was some indentation issue, after selecting everything (all 11000 lines) and pressing TAB twice, C::B just ended (no report, no dialog, just quitting).

    Here how to reproduce:

    - Create a 11K lines test file with this bash script (in Cygwin):

        for i in {1..11000}; do echo "Test $i" >> Test.txt; done

    - Open C::B (no project)
    - Open the file.
    - Select all lines (from 1 to 110000)
    - Press TAB
    - Wait for completion
    - Press TAB again.
    - Wait for C::B to quit.

    C::B 9854 running on WinXP SP 3.

    One problem at a time and we will get there.