Dopus 5 Open Source

[ancalimon]

I wish someone kept maintaining and updating Opus5.
https://sourceforge.net/projects/dopus5allamigas/

If someone helped me with how to set up the proper software, I would try to do something. I am a fast learner.

[Pyromania]

What else does it need?

[pipper]

I did that already some years ago and imported the sourceforge project into GitHub:

https://github.com/mheyer32/dopus5allamigas


I updated the make files and code to build with Bebbo’s GCC cross compilation toolchain and fixed a few bugs here and there.

There’s also a brand new effort based on GPL instead of APL license called “Galileo”

https://github.com/Hagbard-Celin/galileo

It is targeted at compiling natively via SAS/C, though

[Phantasm]

Originally Posted by pipper

I did that already some years ago and imported the sourceforge project into GitHub:

https://github.com/mheyer32/dopus5allamigas


I updated the make files and code to build with Bebbo’s GCC cross compilation toolchain and fixed a few bugs here and there.

There’s also a brand new effort based on GPL instead of APL license called “Galileo”

https://github.com/Hagbard-Celin/galileo

It is targeted at compiling natively via SAS/C, though

Yes your repo seemed to be the most up to date that's the reason I created a pull request with some small changes I had implemented about 6 months ago

[pipper]

Are you the creator of Galileo? Is it this one:
https://github.com/mheyer32/dopus5allamigas/pull/5
?

[Phantasm]

No mine was the one before that. Just a few small enhancements

[hceline]

Originally Posted by pipper

Are you the creator of Galileo? Is it this one:
https://github.com/mheyer32/dopus5allamigas/pull/5
?

That would be me.

Since Galileo was mentioned I must note that I would not recommend using the current v0.1 release.

In spite of all my memory-leak fixes, it looses almost 1,5KB only by starting it and immediately quitting it, and that is the best case.
In the worst case, I just discovered a rare failure-mode where it leaves about 57KB allocated after starting and quitting.

I will tag a new version when I've found and plugged the source of these leaks.

It might be OK for Workbench replacement mode, as one usually do not quit it from that mode. But I've not gotten around to testing that mode, so I have no idea if it works at all.

-Hagbard Celine

[hceline]

The good news is that this looked worse than it was.
The 57KB loss was due to a use-after-free in my self-hacked resource-tracking library, so not a issue with the main codebase.
And when measuring the 1,5KB loss I forgot to account for the auto copy of files from EnvArc: to Env:, so it is quite a bit smaller.

The bad news is that while hunting down the remaining memory leaks, I keep finding the kind of bugs that pushes the goalposts for tagging a new release.

-Hagbard Celine