Menu

#1265 Patch for Linux-3.1.x

Next_Nightly
open
nobody
None
Patch
2022-06-17
2022-05-04
LETARTARE
No

I propose you the set of '*.cbp' files to use 'wx-3.1.x' tested with 'Leap-15.3 'and 'wx-315'
Perhaps there are some oversights !

1 Attachments

Discussion

  • LETARTARE

    LETARTARE - 2022-06-16

    Here is a version generated under 'Leap-15.4, wx317' and 'Cb-12838

     
  • LETARTARE

    LETARTARE - 2022-06-16

    forgot ..

     
  • Andrew Cottrell

    Andrew Cottrell - 2022-06-17

    The existing main unix project file has the following wxWidget version variable name:
    <variable name="WX_VERSION" value="31"></variable>

    This variable can be used in the project file instead of changing the hard coded Wxwidget version like the following:
    3.0 unix project file:
    <option object_output=".objs30">
    3.1 unix project file:
    </option><option object_output=".objs31">
    Use variable and therefore supports both 3.0, 3.1 and in the future 3.2:
    </option><option object_output=".objs$(WX_VERSION)"></option>

    The "other" 30 to 31 changes can also be updated to use $(WX_VERSION).

    The downside of this is that some project files do not have the wxWidget variables defined and a such you will need to add them, but it is a one off change.

    The next issue is that changing from wxWidget 3.0.x to 3.1.x you need to modify all of the project files to update the variables. To fix this you can use global variables, like $(#CB_RELEASE_TYPE), but for wxWidgets. I have allready done this in the https://github.com/acotty/CodeBlocks_Unofficial_Testing repo, which you can use to see what the project files are like for global variables. The repo also has project file changes to copy/create all of the files in the develxx directory instead of calling scripts.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.