Dear Andreas,
Thank you very much for bringing attention to this again.
We actually had a project objective to release a 0.44.16 version of the
SDK by the end of June, but this might slip to the end of July.
We are also in the process of separating the Ecere SDK into more modular
components, which would facilitate adoption of each individual
components (the eC language, the Ecere IDE, the GUI toolkit, the
windowing platform library, the 2D & 3D graphics engine, the networking
library...) and reduce dependencies for software written in eC.
It should also avoid these long delays between releases, which was
largely due to several unrelated in-progress new features and
improvements which we kept debating whether they're ready / clean enough
for an official release.
The new stand-alone eC Compiling tools and Runtime Library is here:
https://github.com/ecere/eC
This will probably not make things easier for Debian packaging, since it
would mean more packages.
However, we were still hoping to do one last ecere-sdk release (this
0.44.16) with the more monolithic "/libecere/" before transitioning to
the separation into modular parts which will be a breaking change.
What we can't really do is fixing problems inside the upstream code.
We are more than happy to take care of that.
However, we usually help to migrate the packaging the Debian development
platform Salsa and I would volunteer to do so for you.
This help would be much welcome!
I have also found some open PRs in Github.
The Pull Requests on GitHub were from Réjean in CC.
Réjean will likely be working with us full-time in July so we can likely
address these soon.
It might be time to tag a new release if several issues are fixed.
Several issues have already been fixed in the "master" branch since the
0.44.15 tag, including those FTBFS issues.
However, there are around 2000 additional commits on the "latest
<https://github.com/ecere/ecere-sdk/commits/latest>" branch, and the
goal for the release was to go through and see what we should or should
not include in 0.44.16.
Another thing we might want to do is fix compilation with OpenSSL 3
instead of relying on OpenSSL 1.1.
The future modular separation will also greatly help with this, in that
only the networking modules will keep a dependency on OpenSSL.
Just let us know about the status and how you want to proceed.
If there is no immediate urgency, could we perhaps plan a quick online
call or IRC chat in early July?
I am a bit swamped right now, and traveling for the next few weeks, back
on July 3rd.
In the meantime (before July), if you're willing to help update (to the
current "master" branch HEAD e399f8dc7f4ecafccdd5a858f22de78bf282fa16
<https://github.com/ecere/ecere-sdk/commits/e399f8dc7f4ecafccdd5a858f22de78bf282fa16>)
/ migrate the packaging the Salsa that would be very welcome.
I could also try to find time earlier to address any issue you may
encounter preventing compilation.
I could also tag the current HEAD of the master branch
(e399f8dc7f4ecafccdd5a858f22de78bf282fa16
<https://github.com/ecere/ecere-sdk/commits/e399f8dc7f4ecafccdd5a858f22de78bf282fa16>)
as 0.44.15.1 or 0.44.15b or whatever would make sense if that would be
useful to do an intermediate bug-fixing release before 0.44.16.
The challenge is that the new official 0.44.16 release is that it would
not only be for Linux, but would also involve a new Windows version of
the installer, including packaging a more recent version of the
MinGW-w64 SDK which would also require some time to package and test.
Thanks again!
Kind regards,
-Jerome
On 6/4/25 3:54 AM, Andreas Tille wrote:
Hi Jérôme,
thank you for maintaining this cool Cross-Platform SDK.
Am Mon, Sep 09, 2024 at 10:35:02AM -0400 schrieb Jérôme St-Louis:
Control: tags -1 + wontfix
I really do hope to update the package to correct the FTBFS bugs, but have
unfortunately been too busy lately.
Please keep the package in unstable, as I really do hope to provide an
updated release that addresses these issues ASAP.
Did you made any progress in fixing the issues?
If anyone is available to help maintaining this package, I would much
appreciate help and would be very keen to assist with that task.
Your package was highlighted in the Bug of the Day[1] initiative, which
aims to introduce newcomers to manageable tasks and guide them through
the workflow to solve them. The focus of this initiative is on migrating
packages to Salsa, as it's a great way to familiarize newcomers with a
consistent Git-based workflow.
What we can't really do is fixing problems inside the upstream code.
However, we usually help to migrate the packaging the Debian development
platform Salsa and I would volunteer to do so for you. However, there
is probably no competence in the eC programming language.
Otherwise, I will certainly get around to it myself, hopefully within the
next 6 months.
The bug fixes for these FTBFS issues should already be in our upstream
master branch<https://github.com/ecere/ecere-sdk/commits/master/>:
I have not found a new tag. What about your self-applied deadline. ;-)
commit ca58cfa4e26e03271e32ee6aae3206956fdc26fd
Author: Jerome St-Louis<jer...@ecere.com>
Date: Wed May 20 07:25:49 2020 -0400
...
and other fixes may also be available from our /latest/ branch
<https://github.com/ecere/ecere-sdk/commits/latest/>.
It might be time to tag a new release if several issues are fixed.
I have also found some open PRs in Github.
Thank you, and apologies for the delays in fixing these issues.
Just let us know about the status and how you want to proceed.
Kind regards
Andreas.
[1]https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks#bug-of-the-day
