OpenEuphoria

2. Re: Euphoria Public Relations

• Posted by useless_ Oct 26, 2013
• 5289 views

I am using:

Euphoria Interpreter v4.0.5 development
Windows, Using Managed Memory
Revision Date: 2013-02-11 02:10:21, Id: 5981:42b209901e89


but no one else seems to have heard of it. It has the replace bug fixed in it.

useless

4. Re: Euphoria Public Relations

• Posted by ryanj Oct 30, 2013
• 5007 views

ONE FREAKING YEAR AGO!!!!!!!!!!!!!!!!!!!!!!! PLZ UPDATE NOW!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

6. Re: Euphoria Public Relations

• Posted by jimcbrown (admin) Nov 01, 2013
• 4874 views

Actually, it more-or-less is finished and ready to ship, as pointed out 5 months ago by mattlewis: http://openeuphoria.org/forum/m/121726.wc

In the interval, jaygade has done a lot of work fixing callbacks in OSX (and other misc OSX work): http://scm.openeuphoria.org/hg/euphoria/rev/4bda3b2a6fa3 , http://scm.openeuphoria.org/hg/euphoria/rev/74222c439548 , http://scm.openeuphoria.org/hg/euphoria/rev/4147657746cb , http://scm.openeuphoria.org/hg/euphoria/rev/40fda2942ba9 , http://scm.openeuphoria.org/hg/euphoria/rev/991791b126ad , http://scm.openeuphoria.org/hg/euphoria/rev/91869ed9ec01 , (and a lot more)...

At this point, we just need someone on the dev team who has enough time to actually build and package the release, and then upload it to sourceforge and update the Downloads page at http://openeuphoria.org/wiki/view/DownloadEuphoria.wc

There's a step-by-step guide on how to package at this wiki page, http://openeuphoria.org/wiki/view/HowToRelease.wc , so even a dev team member who has never performed a release before should be able to do it single handedly.

Also, if you have trouble uploading to sourceforge, I'm sure one of the (very busy) dev team members who has done it before (but lacks the free time to handle the task of doing the complete 4.1.0/4.0.6 release) will be able to scrounge up enough free time to handle that part... or answer any other questions or assist with any other roadblocks that you might hit...

(Who is on the dev team right now that can actually do this big release? Well, ryanj is one of the members...)

8. Re: Euphoria Public Relations

• Posted by jimcbrown (admin) Nov 01, 2013
• 4823 views

Yes, I am. As far as I know, this is indeed the case.

10. Re: Euphoria Public Relations

• Posted by mattlewis (admin) Nov 01, 2013
• 4798 views

I think we should build 4.0.x with Watcom, but IIRC, the policy is to use gcc only for 4.1+. Yes, there will need to be 64-bit releases on Windows and Linux (at least) for 4.1. The debian packaging works for both. I don't know that we've updated the Windows packaging.

We'll need to figure out what to do for OSX and the other BSDs, too.

Matt

12. Re: Euphoria Public Relations

• Posted by _tom (admin) Nov 01, 2013
• 4795 views

Where do documentation changes go?

Is the main SCM "euphoria"? What is the purpose of "euphoria_rebase"?

_tom

14. Re: Euphoria Public Relations

• Posted by jaygade Nov 01, 2013
• 4780 views

I think that OS X is different enough from the BSDs that they shouldn't be lumped together. I saw then when I was last browsing the code and changing stuff around a few weeks ago. Especially with regards to memory management assumptions.

Unfortunately, my interest has waned again and I haven't made any changes in awhile. I was going to go through and do a major source code cleanup and then I got into doing other stuff.

Still, if something needs to be fixed or tested for OS X prior to release, I can do that. I wouldn't suggest releasing 4.06 for OS X, 4.1+ only.

16. Re: Euphoria Public Relations

• Posted by ghaberek (admin) Nov 01, 2013
• 4822 views

We probably need to update the Windows packaging. I am already familiar with InnoSetup. I also think we need a plain zip release for Windows.

I only have an older eMac, but I do not have an Intel-based Mac at my disposal. I would love to see a PowerPC release of Euphoria as well, but I'm not sure if the work done for OSX and ARM have done enough to fix all the issues I had trying to build on PowerPC a couple years ago (but I did get it built and mostly-working). Someone else will have to take the reigns on building an OSX release.

I have an HP TouchPad (ARMv7) and a Raspberry Pi (ARMv6) I can use to test builds for those versions. I make no guarantees on anything else, but those are two popular hacking platforms.

I will see if I can accomplish anything this weekend. I am quite busy but I would like to see a release out soon.

-Greg

18. Re: Euphoria Public Relations

• Posted by jimcbrown (admin) Nov 05, 2013
• 4489 views

Yes.

Yes.

After building. You may need to make minor updates (e.g. bumping up the revision number in various places), which should be committed and pushed before tagging.

20. Re: Euphoria Public Relations

• Posted by _tom (admin) Nov 05, 2013
• 4457 views

I have just created a new pdf of the documentation.

I use wkhtmltopdf. It converts the Creole html into a pdf without any fuss. It is small download, runs from one file, and uses an ordinay css file for style. Exactly what makes sense for a casual user.

I do not have the time to mess with TexLive and such.

I will be editing the documentation all this week...

_tom

22. Re: Euphoria Public Relations

• Posted by mattlewis (admin) Jan 10, 2014
• 3167 views

There's always something in the chain that breaks between releases. In particular, I know that the build system for 4.1 had some significant changes. I recently started running through some of the deployment type build tasks, and I think that the source-tarball (or whatever they are) processes need some work.

Matt

24. Re: Euphoria Public Relations

• Posted by jimcbrown (admin) Jan 15, 2014
• 2973 views

It produces .a files for the static libraries, which is all that's needed.

IIRC the .lib files are only relevant to (and produced by) OpenWatcom. Which is a 4.0.6 only proposition. 4.1.0 is MinGW-only.

Yes.