Recent Posts

Pages: 1 2 3 4 5 [6] 7 8 9 10
51
Nightly builds / Re: The 15 August 2017 build (11146) is out.
« Last post by oBFusCATed on August 15, 2017, 09:12:15 am »
@killerbot: Some of the lines in the change log belong to the release-16.xx branch.
52
Nightly builds / The 15 August 2017 build (11146) is out.
« Last post by killerbot on August 15, 2017, 09:06:45 am »
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_gcc510-TDM-2.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_gcc510-TDM.7z

The 15 August 2017 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2017/CB_20170815_rev11146_win32.7z
  - Linux :
   none

The current SDK version is : 1.31.0

Resolved Fixed:

  • editor: Revert some commits related to copy and pasting on wxGTK (9420, 6883, 5185) (ticket #524)
  • scintilla: Fix middle click copy/pasting when using wx2.8
  • UI: Fix open containing folder on linux (ticket #419)
  • UI: Move the open containing folder setting to the environment dialog (ticket #419)
  • UI: Fix redraw problem on ubuntu because freeze/thaw are used in a wrong way

Regressions/Confirmed/Annoying/Common bugs:


    53
    bad programming, and I am less then  an average programmer and can see that.
    With that attitude, you will never become even a beginner in programming.
    It's often not easy to understand even simple programs, written by others, fully.
    But Code::Blocks is by far not a simple program, with it's core and plugins.
    54
    Development / replace M:\Private\CB\CodeBlocks\CodeBlocks in CodeBlocks_wx31_64.cb
    « Last post by iceant on August 15, 2017, 04:52:59 am »
    Index: CodeBlocks_wx31_64.cbp
    ===================================================================
    --- CodeBlocks_wx31_64.cbp   (revision 11147)
    +++ CodeBlocks_wx31_64.cbp   (working copy)
    @@ -152,7 +152,7 @@
                    <Add directory="sdk/scripting/lib" />
                 </Linker>
                 <ExtraCommands>
    -               <Add before="build_tools\autorevision\autorevision31_64 +wx +int +t M:\Private\CB\CodeBlocks\CodeBlocks include/autorevision.h" />
    +               <Add before="build_tools\autorevision\autorevision31_64 +wx +int +t .. include/autorevision.h" />
                    <Add after="cmd /c if not exist devel31_64\share\CodeBlocks mkdir devel31_64\share\CodeBlocks" />
                    <Add after="zip -jq9 devel31_64\share\CodeBlocks\manager_resources.zip sdk\resources\*.xrc" />
                    <Add after='cmd /c &quot;cd sdk\resources &amp; zip -0 -q ..\..\devel31_64\share\CodeBlocks\manager_resources.zip images\*.png images\12x12\*.png images\16x16\*.png&quot;' />
    55
    and I am less then  an average programmer
    I totally agree on that! And because of that it seems you are missing some basic information about what is going on here.

    CodeBlocks is not a compiler, its basically a frontend for a compiler. The compiler you are using is gcc and the error you are seeing is from gcc, not CodeBlocks.

    Why does code completion of CodeBlocks know about all these X11 headers? Because you told CodeBlocks where to look for them and, big surprise, you told CodeBlocks the correct location?

    But why isnt gcc happy with your headers? Well, the compiling stage is, but the linking stage isnt. Because the linker gives a fuck about your headers, all it cares about is libraries.

    So you only told CodeBlocks where the headers are which CodeBlocks told gcc, but you didnt tell CodeBlocks where the libraries are so gcc complains about.

    So no bad programming here, only bad user here, this cannot be fixed from this side. And before you cry more, it is and has always been the responsibility of the user to setup his compiler environment.
    56
    Still not enough information like cb version, compiler, debugger version, os...

    For wx3.1 you should setup gdb enabled python.
    57

    wx 3.1.0
    i've not tried wx 2.8 it's a relic
    58
    Plugins development / Re: wxSmith
    « Last post by oBFusCATed on August 14, 2017, 11:43:28 pm »
    winnie: Can you show a code example? Link to documentation?
    59
    sam_gonfle:
    I guess not... You've not mentioned any version information for any of the components you've tried.
    wxString changed in wx3.x, so old scripts (for wx2.8) don't work any more.
    Also the defaults in C::B are only meant to work with wx2.8.
    60
    hi,
    I have the same problem.
    wxString are displayed in the watch tab when local under string->m_impl->..->_M_P_.
    If the same string is added as watch , nothing works. If the string is global, nothing works.
    If the cursor hover on the string, i have
    Quote
    [debug]> whatis strTrv
    [debug]type = wxString
    [debug]>>>>>>cb_gdb:
    [debug]> output &strTrv
    [debug](wxString *) 0xdcafb90>>>>>>cb_gdb:
    [debug]> output /c strTrv.m_pchData[0]@((wxStringData*)strTrv.m_pchData - 1)->nDataLength
    [debug]No symbol "wxStringData" in current context.
    [debug]>>>>>>cb_gdb:

    As for every C::B's update, it's a nightmare to be able to  debug the wxString. I  spent a lot of time to make it work for previous versions of C::B or wxWidgets and of course, i don't remember what i've done before. I tried whith another debbuger ( TDM ) with python-> not working.
    copying print.py stuff from wxWidgets -> not working
    forums are most of time a waste of time, problem is known since more then 10 years...
    I don't feel like spending days to configurate a single debugger, so i tried another ide : Netbeans.
    it works perfectly !!!
    Hope i've been a bit more helpfull for tomay3000.
    regards.
    Pages: 1 2 3 4 5 [6] 7 8 9 10