Author Topic: The 21 July 2009 build (5696) is out.  (Read 41875 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5193
The 21 July 2009 build (5696) is out.
« on: July 22, 2009, 12:13:58 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://prdownload.berlios.de/codeblocks/wxmsw28u_gcc_cb_wx2810.7z

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

The 21 July 2009 build is out.
  - Windows :
   http://prdownload.berlios.de/codeblocks/CB_20090721_rev5696_win32.7z
  - Linux :
   none

Resolved Fixed:

  • CodeSnippets 1.3.107 2009/06/22
    - Add "Settings..." to plugin ">" button menu.
    - Use APPDATA envar on first run since CodeBlocks returns "" for config folder in OnAttach()
  • merged wxfnb_to_wxaui branch to trunk
  • added missing files in debian install-file (got lost in merge); reverted 5683 (the files have been renamed in 5671 and are therefore not missing)
  • fix broken context-menus in infopane; make sure that starthere-page is hidden if a new project is created; replace tabs with spaces
  • fix a background-coloring issue (not the whole background was coloured, only bg containing characters, see http://forums.codeblocks.org/index.php/topic,10810.msg74145.html#msg74145)
  • BrowseTracker 1.2.78 2009/07/13
    - Fix activations by keyboard after wxAuiNotebook added.
    - Sort browse marks in idle time.
  • fix a possible crash-candidate
  • indentation guide highlight

Regressions/Confirmed/Annoying/Common bugs:



    Offline killerbot

    • Administrator
    • Lives here!
    • *****
    • Posts: 5193
    Re: The 21 July 2009 build (5696) is out.
    « Reply #1 on: July 22, 2009, 12:14:24 pm »
    FYI : next nightly will most likely be build with GCC MinGW 4.4.0

    Offline ahui886

    • Multiple posting newcomer
    • *
    • Posts: 29
    Re: The 21 July 2009 build (5696) is out.
    « Reply #2 on: July 22, 2009, 12:19:54 pm »
    FYI : next nightly will most likely be build with GCC MinGW 4.4.0
    great!
    good job!
    thx.

    Offline jens

    • Administrator
    • Lives here!
    • *****
    • Posts: 7265
      • Jens' unofficial debian-repository for the Code::Blocks - IDE
    Re: The 21 July 2009 build (5696) is out.
    « Reply #3 on: July 22, 2009, 02:36:17 pm »
    Just moved the debian-build on my server (see signature) into the repo.

    They are build on lenny-pbuilder and linked against wxWidgets 2.8.10.

    The revision for my builds is 5694.
    The only missing part is the indendation guide highlight (the indendation guide is still working of course).

    Uploading the latest version will take me about 5 hours due to my fantastic ISDN connection.
    It will most likely come this evening / night.

    Offline ollydbg

    • Developer
    • Lives here!
    • *****
    • Posts: 5247
    • OpenCV and Robotics
      • Chinese OpenCV forum moderator
    Re: The 21 July 2009 build (5696) is out.
    « Reply #4 on: July 22, 2009, 02:55:05 pm »
    FYI : next nightly will most likely be build with GCC MinGW 4.4.0
    If we use the nightly build version build from GCC MinGW 4.4.0, do we need to use a "Dwarf-2 Unwinding TDM-GCC"?

    Because by default, the current TDM-GCC was still using "SJLJ".

    I have suggest John to set "Dwarf-2 Unwinding TDM-GCC" as a default install package, but seems there's no response. :(
    If some piece of memory should be reused, turn them to variables (or const variables).
    If some piece of operations should be reused, turn them to functions.
    If they happened together, then turn them to classes.

    Offline Xaviou

    • Regular
    • ***
    • Posts: 302
      • X@v's wxStuff
    Re: The 21 July 2009 build (5696) is out.
    « Reply #5 on: July 22, 2009, 07:23:10 pm »
    Ubuntu 8.04 to 9.04 Amd64 tar.gz archive (containing '.deb' installers builds with wx2810) can be found  here (direct link).
    The french wxWidgets site : http://www.wxdev.fr
    My wxWidgets's stuff : https://wxstuff.xaviou.fr/

    Offline geiermeier

    • Multiple posting newcomer
    • *
    • Posts: 19
    Re: The 21 July 2009 build (5696) is out.
    « Reply #6 on: July 23, 2009, 08:58:58 am »
    Shouldn't this version contain the possibility to have more than one editor pane? If so I can't find out how to achieve this.

    And somehow I can't comment/uncomment anymore, not with shortcut nor with menu. This happens after I use the settings to choose between docking the symbols browser and having it as separate window. Seems like both directions of changing this option break the ability to comment out code (using the line comment // ).

    Actually it happens even after going into the editor options without changing anything...
    It only happens sometimes. If you can't reproduce, I'll look some further into this.

    Restarting CB helps then.
    « Last Edit: July 23, 2009, 09:13:28 am by geiermeier »

    Offline jens

    • Administrator
    • Lives here!
    • *****
    • Posts: 7265
      • Jens' unofficial debian-repository for the Code::Blocks - IDE
    Re: The 21 July 2009 build (5696) is out.
    « Reply #7 on: July 23, 2009, 10:38:26 am »
    Shouldn't this version contain the possibility to have more than one editor pane? If so I can't find out how to achieve this.
    Move the mouse over an editors tab, press the left mouse-button and drag it (the tab) with pressed button to another place in the editor pane.
    And somehow I can't comment/uncomment anymore, not with shortcut nor with menu. This happens after I use the settings to choose between docking the symbols browser and having it as separate window. Seems like both directions of changing this option break the ability to comment out code (using the line comment // ).

    Actually it happens even after going into the editor options without changing anything...
    It only happens sometimes. If you can't reproduce, I'll look some further into this.

    Restarting CB helps then.

    I can confirm this issue and will have alook into it (doesn't even work from menu).

    Offline jens

    • Administrator
    • Lives here!
    • *****
    • Posts: 7265
      • Jens' unofficial debian-repository for the Code::Blocks - IDE
    Re: The 21 July 2009 build (5696) is out.
    « Reply #8 on: July 23, 2009, 01:42:10 pm »
    And somehow I can't comment/uncomment anymore, not with shortcut nor with menu. This happens after I use the settings to choose between docking the symbols browser and having it as separate window. Seems like both directions of changing this option break the ability to comment out code (using the line comment // ).

    Actually it happens even after going into the editor options without changing anything...
    It only happens sometimes. If you can't reproduce, I'll look some further into this.

    Restarting CB helps then.

    I can confirm this issue and will have alook into it (doesn't even work from menu).

    Should (hopefully) be fixed in trunk (r5701) and cc-branch (r5702).

    Offline dirk_1980

    • Multiple posting newcomer
    • *
    • Posts: 25
    Re: The 21 July 2009 build (5696) is out.
    « Reply #9 on: July 23, 2009, 04:50:09 pm »
    Hi

    I am disappoints of y'all,  because a alleged easy "save with backup",  is not build in after now  2 new versions.

    I am also disappoints over y'all, because I thought CodeBlocks would be my editor for my embedded projects.
    But you don't build in the  "#Ifdef #else #endif " evaluation.

    Thus I will stwitch to Netbeans for my embedded projects, not for my Windows projects!

    Best wishes,
    Dirk

    Offline Xaviou

    • Regular
    • ***
    • Posts: 302
      • X@v's wxStuff
    Re: The 21 July 2009 build (5696) is out.
    « Reply #10 on: July 23, 2009, 11:50:09 pm »
    Hi all
    I have a strange behaviour with the Help plugin under Windows.

    Here is the context :
    I've defined the wxWidgets "chm" help file as the "main" help file to be used (pressing the F1 key will search for the selected word in this file).
    I've also defined another "chm" help file with this plugin, but for this one, no option is selected (I just select a word in the editor, and go to Help -> Name of the help file).

    And now, here is the problem :
    I first open the "secondary" help file by selecting a keyword, and go into the help menu
    Then, I select another keyword, and press the F1 key to open the main help file.
    There is a message shown 2 times before the help file comes.
    The title of the MessageBox is : HTML Help Author Message
    And the text is :The window name "main" passed to HH_GET_WIN_TYPE has not been specified.
    As I said, this message is shown 2 times, and after that, the help file is opened correctly.

    If I first open the main help file, and then the secondary, there is no problems, and the help files are shown correctly without message.

    I hope I explained myself correctly : if not, let me know.  :?

    Can someone confirm this ?

    Regards
    Xav'
    The french wxWidgets site : http://www.wxdev.fr
    My wxWidgets's stuff : https://wxstuff.xaviou.fr/

    Offline chikigai

    • Multiple posting newcomer
    • *
    • Posts: 33
    Re: The 21 July 2009 build (5696) is out.
    « Reply #11 on: July 24, 2009, 01:30:18 am »
    And somehow I can't comment/uncomment anymore, not with shortcut nor with menu. This happens after I use the settings to choose between docking the symbols browser and having it as separate window. Seems like both directions of changing this option break the ability to comment out code (using the line comment // ).

    Actually it happens even after going into the editor options without changing anything...
    It only happens sometimes. If you can't reproduce, I'll look some further into this.

    Restarting CB helps then.

    I can confirm this issue and will have alook into it (doesn't even work from menu).

    Should (hopefully) be fixed in trunk (r5701) and cc-branch (r5702).


    Hello,

    I noticed this from a couple of nightly builds back and filed a bug report which can now be closed:

    http://developer.berlios.de/bugs/?func=detailbug&bug_id=16032&group_id=5358
    [Development Environment]
    OS: WinXP SP3
    IDE: Code::Blocks Nightly Build SVN Rev.6080 wxWidgets: 2.8.10 Windows Unicode Build SVN: 1.6.x

    Offline kad77

    • Single posting newcomer
    • *
    • Posts: 3
    Re: The 21 July 2009 build (5696) is out.
    « Reply #12 on: July 24, 2009, 03:59:25 am »
    Hi, I've been a Dev-C++ guy for years, and as long as I can keep plugging in new mingw builds and use MSYS, I'm happy. I really appreciate how the CB people are trying to evolve an IDE to meet the needs of the non-MSVC subclass like myself. ;-)

    I am considering using CodeBlocks now that I have some new projects and will be spending time in the IDE again. I mostly write cross-platform code from Windows, and have little use for Visual Studio or Eclipse despite some of their nifty features, due to their incompatibilities.

    From an outsiders perspective, the release cycle management of CB is frustrating. Many of us want to see where things are at this year, but don't want to work with SVN (just read about the comment/uncomment bug). Despite all of the SVN activity, it's been almost 1.5 years since a formal release!! I might as well stick with ancient DevCpp, which I know, than learn an old release of CB thats missing current features...

    Can the devs please consider letting some potential new users in the gate? Having a feature freeze, and just fixing regressions and bugs so a proper release can happen? any time now? Many die-hard Dev-Cpp users would really appreciate a modern, current, stable CB 8.x release so we can jump in.

    I realize CB from 2/08 is out. This request is out of principle. Why let the hard work of many months be hidden from 'outsiders'??


    Apologies if my feedback sounds like negativity. I just want to remind you of the plebs out here that just want to use the product and give feedback, not necessarily write the IDE & their apps. ;-)

    Offline Loaden

    • Lives here!
    • ****
    • Posts: 1014
    Re: The 21 July 2009 build (5696) is out.
    « Reply #13 on: July 24, 2009, 05:12:38 am »
    The 'User templates' can't portable, it's must saved in %APPDATA%\codeblocks ?
    Why can't saved to: $(CODEBLOCKS)\share\ ?

    Offline geiermeier

    • Multiple posting newcomer
    • *
    • Posts: 19
    Re: The 21 July 2009 build (5696) is out.
    « Reply #14 on: July 24, 2009, 10:38:46 am »
    From an outsiders perspective, the release cycle management of CB is frustrating. Many of us want to see where things are at this year, but don't want to work with SVN (just read about the comment/uncomment bug). Despite all of the SVN activity, it's been almost 1.5 years since a formal release!! I might as well stick with ancient DevCpp, which I know, than learn an old release of CB thats missing current features...

    I've never used SVN access to the sources and I've never build a binary version myself. Just use the nightly builds, that are advertised in this forum.

    Maybe they should call them differently and just release them as normal versions, because that's basically what they are.

    Offline Alexis

    • Multiple posting newcomer
    • *
    • Posts: 62
    Re: The 21 July 2009 build (5696) is out.
    « Reply #15 on: July 24, 2009, 12:01:11 pm »
    Quote
    I've never used SVN access to the sources and I've never build a binary version myself. Just use the nightly builds, that are advertised in this forum.
    Yes, getting the archive makes SVN unnecessary.

    Quote
    Maybe they should call them differently and just release them as normal versions, because that's basically what they are.
    No, they are not. Regular "official" releases are usually preceded by alpha, beta and release candidates. There is no evolution anymore, only bug fixing, and software is thoroughly, extensively tested.

    With nightly builds, you have bug fixing, but also new features. So you can never be sure you will not face regressions. With official releases, you can expect a quite high confidence level in the soft.


    Offline jens

    • Administrator
    • Lives here!
    • *****
    • Posts: 7265
      • Jens' unofficial debian-repository for the Code::Blocks - IDE
    Re: The 21 July 2009 build (5696) is out.
    « Reply #16 on: July 24, 2009, 12:29:18 pm »
    I noticed this from a couple of nightly builds back and filed a bug report which can now be closed:

    http://developer.berlios.de/bugs/?func=detailbug&bug_id=16032&group_id=5358


    Done, thank you for reminding !

    Offline kad77

    • Single posting newcomer
    • *
    • Posts: 3
    Re: The 21 July 2009 build (5696) is out.
    « Reply #17 on: July 24, 2009, 01:02:33 pm »
    Quote
    Maybe they should call them differently and just release them as normal versions, because that's basically what they are.
    No, they are not. Regular "official" releases are usually preceded by alpha, beta and release candidates. There is no evolution anymore, only bug fixing, and software is thoroughly, extensively tested.

    With nightly builds, you have bug fixing, but also new features. So you can never be sure you will not face regressions. With official releases, you can expect a quite high confidence level in the soft.

    You stated my point better than I. Many people don't want to roll the dice with SVN builds (precompiled or not). I assume sometimes CB undergoes minor surgery for new features, making nightlies unstable for a while.

    I read the wikipedia article, and it seems 'endless beta' is in the culture here @ CB, but for the sake of users, or to grow potential users consider a 9.08 release that doesn't have blockers or regressions. Thanks for reading.  :P

    Offline geiermeier

    • Multiple posting newcomer
    • *
    • Posts: 19
    Re: The 21 July 2009 build (5696) is out.
    « Reply #18 on: July 24, 2009, 01:03:46 pm »
    No, they are not. Regular "official" releases are usually preceded by alpha, beta and release candidates. There is no evolution anymore, only bug fixing, and software is thoroughly, extensively tested.

    The updates for e.g. TortoiseSVN (which is probably very widely used) are bugfix+feature updates. And everyone gets a new version number and is official. I'd say they're about equal to CB's nightlies even with a similar frequency.

    Offline kad77

    • Single posting newcomer
    • *
    • Posts: 3
    Re: The 21 July 2009 build (5696) is out.
    « Reply #19 on: July 24, 2009, 02:34:48 pm »
    No, they are not. Regular "official" releases are usually preceded by alpha, beta and release candidates. There is no evolution anymore, only bug fixing, and software is thoroughly, extensively tested.
    The updates for e.g. TortoiseSVN (which is probably very widely used) are bugfix+feature updates. And everyone gets a new version number and is official. I'd say they're about equal to CB's nightlies even with a similar frequency.

    Your saying that TortoiseSVN's managed tested, formal point releases are the same as the nightly build dumps done here? Perhaps you should reconsider your statement. I'd encourage you to read two pages: http://tortoisesvn.net/downloads && http://tortoisesvn.net/status

    Take note of the changelogs, release notes, nightly build policy, their release history-- Notice the alpha, beta, and RCs in there.

    If anything, the CB user community would be far better served by following the TortoiseSVN release management structure. Sorry for being repetitive here. I wish responses to the logic of my suggestion were more prevalent than those dismissing it, or rationalizing the current SVN dumps.

    Offline Zini

    • Multiple posting newcomer
    • *
    • Posts: 64
    Re: The 21 July 2009 build (5696) is out.
    « Reply #20 on: July 24, 2009, 09:49:49 pm »
    Quote
    If anything, the CB user community would be far better served by following the TortoiseSVN release management structure.

    Why? Who cares if a new nightly suddenly has some bugs? It is trivially easy to go back to an older version.

    TortoiseSVN is a totally different topic. For a start TortoiseSVN is rather "hard" to install. It inserts itself deeply into the system and even requires a reboot. If anything goes wrong here, that could be rather fatal.
    But Code::Blocks? Okay, maybe some function will fail. That is hardly a drama. Going back to an older version takes at most two minutes (less, if you keep the older version installed in parallel).
    And the chance for a data-loss or any other kind of damage is rather minimal too. Please note, that the embedded text-editor is a separate project, which AFAIK is going through a more ridigd release procedure. Adding to this any sane developer will use some kind of version control system, so even in the rather unlikely event, that some files are damaged, the damage would be limited to the work since the last commit.
    Sorry, but worrying about the risk and the consequences of a malefunctioning nightly is extremly irrational in my opinion.

    I would prefer it if the regular releases would be completely abolished. There are a waste of developer time IMHO.

    Willy1234

    • Guest
    Re: The 21 July 2009 build (5696) is out.
    « Reply #21 on: July 25, 2009, 02:27:47 am »
    I think that if C::B's nightlies are released as updates an update tool needs to be built into C::B  that is similar to the Mozilla Firefox one. Maybe also switching back to a standard version number convention (i.e. 1.x, 2.x, 3.x) rather than the Ubuntu version number convention. But what do I know, I'm just a user of the C::B nightlies not a dev. Oh and quick question, I just installed the most recent and I get a pop-up saying that wxSmithAui.dll was not loaded due to being an old version. Where can I get the newest build of that .dll?

    Offline Loaden

    • Lives here!
    • ****
    • Posts: 1014
    Re: The 21 July 2009 build (5696) is out.
    « Reply #22 on: July 25, 2009, 12:27:50 pm »
    Crash Report:
    1. Open CB and Close any page
    2. View - Switch Tabs
    3. Click 'Open files'
    4. Crash!

    Redo it.


    [attachment deleted by admin]

    Offline ollydbg

    • Developer
    • Lives here!
    • *****
    • Posts: 5247
    • OpenCV and Robotics
      • Chinese OpenCV forum moderator
    Re: The 21 July 2009 build (5696) is out.
    « Reply #23 on: July 25, 2009, 12:35:38 pm »
    Crash Report:
    1. Open CB and Close any page
    2. View - Switch Tabs
    3. Click 'Open files'
    4. Crash!

    Redo it.


    I can confirm this bug.
    If some piece of memory should be reused, turn them to variables (or const variables).
    If some piece of operations should be reused, turn them to functions.
    If they happened together, then turn them to classes.

    Offline jens

    • Administrator
    • Lives here!
    • *****
    • Posts: 7265
      • Jens' unofficial debian-repository for the Code::Blocks - IDE
    Re: The 21 July 2009 build (5696) is out.
    « Reply #24 on: July 25, 2009, 12:53:04 pm »
    Crash Report:
    1. Open CB and Close any page
    2. View - Switch Tabs
    3. Click 'Open files'
    4. Crash!

    Redo it.


    I can confirm this bug.
    I can confirm it on w2k and linux, but it always crashes if I click on "Open files", egally if I have closed or opened any tab, even if no project is loaded.

    I will look into it.

    Offline jens

    • Administrator
    • Lives here!
    • *****
    • Posts: 7265
      • Jens' unofficial debian-repository for the Code::Blocks - IDE
    Re: The 21 July 2009 build (5696) is out.
    « Reply #25 on: July 25, 2009, 02:47:05 pm »
    Should be fixed in cc-branch (r5703) and trunk (r5704).

    Offline Jewe

    • Multiple posting newcomer
    • *
    • Posts: 70
      • Fit Trainer
    Re: The 21 July 2009 build (5696) is out.
    « Reply #26 on: October 14, 2009, 12:20:27 pm »
    The compiler settings(number of CPU for parallel build) are stored user depending and not machine depending.
    I have a 4 core development machine, a 2 core laptop and a 1 core nightly build machine and all 3 machines have my profile.
    can this be solved? so I can configure this for every machine independent?

    cheers,

    Jewe
    Anything curved in the hardware can be straighten with software :D
    OS: Vista64 + Debian(to play with)
    Compiler: mingw IDE: Code::Blocks Nightly WX: 2.8.0

    Offline oBFusCATed

    • Developer
    • Lives here!
    • *****
    • Posts: 12122
      • Travis build status
    Re: The 21 July 2009 build (5696) is out.
    « Reply #27 on: October 14, 2009, 01:21:28 pm »
    No, because a user program can't change system files when the user is not an administrator (on all machines that != windows xp :) )
    (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 jens

    • Administrator
    • Lives here!
    • *****
    • Posts: 7265
      • Jens' unofficial debian-repository for the Code::Blocks - IDE
    Re: The 21 July 2009 build (5696) is out.
    « Reply #28 on: October 14, 2009, 01:41:26 pm »
    You can use different personalities for different setups.
    codeblocks --help shows the appropriate command-line parameters.

    Offline Jewe

    • Multiple posting newcomer
    • *
    • Posts: 70
      • Fit Trainer
    Re: The 21 July 2009 build (5696) is out.
    « Reply #29 on: October 26, 2009, 04:30:34 pm »
    You can use different personalities for different setups.
    codeblocks --help shows the appropriate command-line parameters.
    Thanks for the suggestion, but I still feel that it should be possible automatically.
    Maybe its an option to have default, and a machine depended setting.
    where the machine depended parameter is the ID of your CPU or something.
    « Last Edit: October 26, 2009, 04:40:34 pm by Jewe »
    Anything curved in the hardware can be straighten with software :D
    OS: Vista64 + Debian(to play with)
    Compiler: mingw IDE: Code::Blocks Nightly WX: 2.8.0

    Offline stahta01

    • Lives here!
    • ****
    • Posts: 6671
      • My Best Post
    Re: The 21 July 2009 build (5696) is out.
    « Reply #30 on: October 26, 2009, 06:16:02 pm »
    You can use different personalities for different setups.
    codeblocks --help shows the appropriate command-line parameters.
    Thanks for the suggestion, but I still feel that it should be possible automatically.
    Maybe its an option to have default, and a machine depended setting.
    where the machine depended parameter is the ID of your CPU or something.

    Please feel free to create the patch for you to use yourself and submit it to Berlios and maybe it will get applied to Code::Blocks.

    Tim S.
    C Programmer working to learn more about C++ and Git.
    On Windows 7 64 bit and Windows 10 32 bit.
    On Debian Stretch, compiling CB Trunk against wxWidgets 3.0.
    --
    When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

    Offline MortenMacFly

    • Administrator
    • Lives here!
    • *****
    • Posts: 9508
    Re: The 21 July 2009 build (5696) is out.
    « Reply #31 on: October 26, 2009, 08:03:24 pm »
    can this be solved? so I can configure this for every machine independent?
    Search the WiKi for "portable".
    Alternatively look here:
    http://wiki.codeblocks.org/index.php?title=FAQ#Q:_How_do_I_make_Code::Blocks_portable.3F
    Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
    C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
    C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ