Author Topic: The 18 october 2006 build is out.  (Read 21873 times)

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5490
The 18 october 2006 build is out.
« on: October 18, 2006, 07:43:43 pm »
Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

A link to the unicode windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw26u_gcc_cb_wx2.6.3p2.7z

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

For support of ansi builds, a link to the ansi windows wxWidget dll for Code::Blocks : http://prdownload.berlios.de/codeblocks/wxmsw26_gcc_cb_wx2.6.3p2.7z

The 18 October 2006 build is out.
  - Windows : http://prdownload.berlios.de/codeblocks/CB_20061018_rev3104_win32.7z
  - Linux :
         http://prdownload.berlios.de/codeblocks/CB_20061018_rev3104_Ubuntu6.06.deb (not yet)
         http://prdownload.berlios.de/codeblocks/CB_20061018_rev3104_suse100+101.rpm (not yet)
         http://prdownload.berlios.de/codeblocks/CB_20061018_rev3104_fc4+5.rpm (not yet)


Resolved Fixed:

  • fixed replace bug (described at http://forums.codeblocks.org/index.php?topic=4243.msg33456#msg33456)
  • Added two new options in plugins management dialog:
      - Install plugin for all users or current user only (checks user rights too).
      - Ask for confirmation if conflicts arise.
  • Console-runner shows return value and execution time of executed process
      console window title shows executed commandline (MSW only)
  • Special pre/post build command added: #run_script. Usage: "#run_script filename.script". Allows to run a Code::Blocks script during the build process. A usage example will be posted on the wiki soon
  • New script function: InstallPlugin(). When called from a script, a security warning is emitted (no way to turn this off)
  • Fixed minor bug in build scripts clearing
  • Few more macros added in MacrosManager:
      - TARGET_OUTPUT_FILE: active target's output filename.
      - TARGET_OUTPUT_BASENAME: active target's output base name (no path and no extension).
      - [target_name]_OUTPUT_BASENAME: named target's output base name (no path and no extension)

Regressions/Confirmed/Annoying/Common bugs:

  • toolbar-images-not-changing-state (is a wx problem/Win XP problem)
  • menu items with icon not correctly aligned (since wx263)


Offline tiwag

  • Developer
  • Lives here!
  • *****
  • Posts: 1196
  • sailing away ...
    • tiwag.cb
Re: The 18 october 2006 build is out.
« Reply #1 on: October 18, 2006, 07:45:11 pm »
@killerbot : does the batchbuild work with this NB ?

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5490
Re: The 18 october 2006 build is out.
« Reply #2 on: October 18, 2006, 07:53:56 pm »
@killerbot : does the batchbuild work with this NB ?

no idea (I still build from within CB ...), still not automated, always postponing it ...

These are the last changes (rev 3104) :
Quote
* Special pre/post build command added: #run_script. Usage: "#run_script filename.script". Allows to run a Code::Blocks script during the build process. A usage example will be posted on the wiki soon.
* New script function: InstallPlugin(). When called from a script, a security warning is emitted (no way to turn this off).
* Fixed minor bug in build scripts clearing.
* Few more macros added in MacrosManager:
- TARGET_OUTPUT_FILE: active target's output filename.
- TARGET_OUTPUT_BASENAME: active target's output base name (no path and no extension).
- [target_name]_OUTPUT_BASENAME: named target's output base name (no path and no extension).

Offline tiwag

  • Developer
  • Lives here!
  • *****
  • Posts: 1196
  • sailing away ...
    • tiwag.cb
Re: The 18 october 2006 build is out.
« Reply #3 on: October 18, 2006, 07:58:42 pm »
@killerbot : does the batchbuild work with this NB ?
no idea (I still build from within CB ...), still not automated, always postponing it ...
i thought when you've built it, you can test it also  :shock:

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5490
Re: The 18 october 2006 build is out.
« Reply #4 on: October 18, 2006, 08:00:29 pm »
there are so many features to test, if I need to test them all, well then it's already time for the next nightly ;-)

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: The 18 october 2006 build is out.
« Reply #5 on: October 18, 2006, 08:00:41 pm »
i thought when you've built it, you can test it also  :shock:
...unless he doesn't like C::B to integrate into explorer... ;-)
Anyway: It works for me, same revision, but self-made. Do you use the nightly or a self-build variant?
With regards, Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline tiwag

  • Developer
  • Lives here!
  • *****
  • Posts: 1196
  • sailing away ...
    • tiwag.cb
Re: The 18 october 2006 build is out.
« Reply #6 on: October 18, 2006, 08:02:06 pm »
Do you use the nightly or a self-build variant?
guess

Offline tiwag

  • Developer
  • Lives here!
  • *****
  • Posts: 1196
  • sailing away ...
    • tiwag.cb
Re: The 18 october 2006 build is out.
« Reply #7 on: October 18, 2006, 08:12:06 pm »
there are so many features to test, if I need to test them all, well then it's already time for the next nightly ;-)
yeah, i don't expect that you test every feature before you release a NB,
but when i ask you for a specific test, it should be doable, isn't it ?

you answered already in the other thread,
so many thanks !

brgds, tiwag

Offline Grom

  • Almost regular
  • **
  • Posts: 206
RC3
« Reply #8 on: October 18, 2006, 11:08:46 pm »
Pls put one of those night builds as a RC3 build. That is not trivial task for new users to install C::B from night builds. Specially the RC2 is a lot  worse then Night Builds....  :?
gcc+winXP+suse.

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9694
Re: RC3
« Reply #9 on: October 18, 2006, 11:16:25 pm »
Pls put one of those night builds as a RC3 build. That is not trivial task for new users to install C::B from night builds. Specially the RC2 is a lot  worse then Night Builds....  :?
I guess this would be a bad idea. Now we have the one or other user that doesn't read through the webpage/forum/wiki where are written several article several times on how to install a nightly build (you basically need to extract it in an empty folder and that's it - where's the problem?).
I we would take a nightly as RC3 we would get a lot more users telling - hey, I found a bug here a bug there... it has to consolidate first, don't you think?!
With regards, Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: https://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: https://wiki.codeblocks.org/index.php?title=FAQ

Offline killerbot

  • Administrator
  • Lives here!
  • *****
  • Posts: 5490
Re: The 18 october 2006 build is out.
« Reply #10 on: October 18, 2006, 11:18:33 pm »
there are so many features to test, if I need to test them all, well then it's already time for the next nightly ;-)
yeah, i don't expect that you test every feature before you release a NB,
but when i ask you for a specific test, it should be doable, isn't it ?

you answered already in the other thread,
so many thanks !

brgds, tiwag

but your request came after the nightly was kicked out  :?

I interpreted your original question as : "maybe you build the nightlies through an automated system that uses a batchbuild. Therefor you might be able to tell me if the batch building worked."
So I anwered, it's not automated, so no use of a batch build, henceforth can tell if it works.

But after the next reply I have tried it ou (see other thread).
« Last Edit: October 18, 2006, 11:30:24 pm by killerbot »

Offline tiwag

  • Developer
  • Lives here!
  • *****
  • Posts: 1196
  • sailing away ...
    • tiwag.cb
Re: The 18 october 2006 build is out.
« Reply #11 on: October 18, 2006, 11:38:09 pm »
but your request came after the nightly was kicked out  :?

yes, because i got my first troubles with exactly the same version as you kicked out  :)

anyhow - thanks a lot for helping me -
it was a nasty bug and i really didn't know where i should start searching !

if you've read the other thread,
you know already, batchbuilding is working fine (in general) ...

brgds, tiwag

Gull_Code

  • Guest
Re: The 18 october 2006 build is out.
« Reply #12 on: October 19, 2006, 10:33:18 am »
Hi all, I am not that new to code::blocks, but it is the first time I encountered and error without beeing able to solve it.

At the startup I got :
Code
ERROR: Plugin resource not found: compilergcc.zip
ERROR: Plugin resource not found: debuggergdb.zip
ERROR: Plugin resource not found: pluginwizard.zip

I saw that the problem has already been solved in some last posts, but I do not understand the way. ( I am French, so excuse my English, I am trying my best to provide you an understandable one )

EDIT: I am using a fresh install of code::blocks (last stable setup from the site) with the last nightly build unzipped inside.
« Last Edit: October 19, 2006, 10:35:15 am by Gull_Code »

cpprooky

  • Guest
Re: The 18 october 2006 build is out.
« Reply #13 on: October 19, 2006, 10:36:26 am »
In french ...

Tu dois nettoyer le dossier dans lequel tu installes la Night Build de C::B.
D'un buld à l'autre, il y a des fichiers qui changent, qui sont ajoutés mais ils y en a aussi qui sont supprimés !
donc, efface le contenu de ton dossier d'install de tes Night Builds, dézippe à nouveau la dernière Night build (sans oublié les dll qui vont bien) et cela devrait être OK.

Offline 354

  • Single posting newcomer
  • *
  • Posts: 6
Re: The 18 october 2006 build is out.
« Reply #14 on: October 19, 2006, 03:13:47 pm »
I've recently started using Code::Blocks and enjoy it very much, so thanks for all the hard work you're putting into this tool.

I'm playing around with the nightly builds to keep myself updated with the latest and greatest, but I thought I would drop you a line concerning this build where I've found a little visual bug. I don't know whether this is known or not (please point me to the correct location to report/discuss bugs if this is not the place for them), but the "X" button on source file tabs on the top of the editor pane/window appears where it shouldn't.

It's reproducible (at least for me) by opening as much files as are needed in order to get at least two pages of tabs in the tabs pane (so you need to use the arrows to the right in the tabs pane to switch between the pages). Select a page and a tab, change to a different page, then move the mouse pointer inside the tab pane, followed by moving the mouse pointer anywhere outside the tabs pane. At this point, the "X" button from the previous page becomes visible on the current page at the same location, but it's (thankfully) not clickable.

I'm using todays build (unicode) and windows XP sp2. I've tried all the different tab "skin" flavours available in the environment options dialog and get the same results with each one of them. Hope this helps.