macOS + Fortran contributions

[perazz]

Hi all,

after long time I've eventually achieved a setup that lets me contribute to CodeBlocks (it's a great code!) and use it profitably on macOS.

To build it successfully I have generated some .cbp macOS project files, and fixes to actually run it (some wxTimer issues would cause segfaults when compiled with clang++).
And, I would like to contribute some advances to the Fortran plugin.

So my question is, how does the SourceForge workflow work? I currenlty use a svn->git repository but I can submit patches either here on the Forum, or on SourceForge directly.

Thank you in advance and let's please discuss what you think is the best approach.

Best,
Federico

[Miguel Gimenez]

Any contribution is welcome, specially those from Mac developers.

The best method for contributing, at least for the initial ones, is posting Subversion patches in the ticket page. Posting in the forum is also valid, but once a post disappears from the main window it will probably be forgotten.

[perazz]

Sounds good, thank you.

So I will open a ticket with the patch file attached.

for Fortran plugin updates, should I also send ticket to the master C::B repository?

[Miguel Gimenez]

Fortran project is a contributed plugin with its own developer and site. Some of us have write access to the repository, but we usually only modify parts not related to the fortran core (p.e. HiDPI changes).

[perazz]

Great - I submitted a few patches, thank you for looking into it.

Do let me know if I should split them into smaller steps (I had to introduce quite a few changes to the `wxTimer` logic in code completion in order to remove the null-pointer crashes).

One of them is to update zlib to 1.3.1 (minimum supported on macOS) and I could branch that out too.

[Miguel Gimenez]

The patch related to wxTimer is too big, if you can split it in chunks it would be easier to check.

Did the zlib update break something?.