Euphoria Programming Language

Hey Matt,

I'll work on building a version tonight when I get home, I'm on my way out
to work right now.  I should have a build going after 7pm EST.

L8ers,

Mario

On Sun, Aug 29, 2010 at 7:38 AM, Matt Lewis <matthewwalkerlewis@...:

> I updated the downloads page and posted an item in the forum.  We
> still need to get the OSX version posted (Mario, you should be able to
> upload now), and also the Linux tar.gz.  Possibly also a windows
> source package (pre-translated).
>
> --
> Matt Lewis
>
>
> ------------------------------------------------------------------------------
> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> Be part of this innovative community and reach millions of netbook users
> worldwide. Take advantage of special opportunities to increase revenue and
> speed time-to-market. Join now, and jumpstart your future.
> http://p.sf.net/sfu/intel-atom-d2d
> _______________________________________________
> Rapideuphoria-develop mailing list
> Rapideuphoria-develop@...
> https://lists.sourceforge.net/lists/listinfo/rapideuphoria-develop
>



-- 
Mario Steele
Lieutenant Commander 3
XO - Geo 99
XO - STO IFT Fleet
http://www.trekfederation.com
http://geo99.ruby-im.net

On Sun, 29 Aug 2010 21:38:56 +1000, Matt Lewis  
<matthewwalkerlewis@...> wrote:

> Possibly also a windows source package (pre-translated).

What do you mean by this? What would it contain exactly?

BTW, I got a clean package by doing an SVN export to a new directory so I  
avoided the build artefacts and my own junk as well.


-- 

Derek Parnell

On Mon, Aug 30, 2010 at 11:02 AM, Derek Parnell <ddparnell@...> wrote:
> On Sun, 29 Aug 2010 21:38:56 +1000, Matt Lewis
> <matthewwalkerlewis@...> wrote:
>
>> Possibly also a windows source package (pre-translated).
>
> What do you mean by this? What would it contain exactly?

Basically something that someone could download and build without
having a working interpreter (i.e., just using OpenWatcom).  This may
not be a big deal for windows, since people are used to getting
binaries.

> BTW, I got a clean package by doing an SVN export to a new directory so I
> avoided the build artefacts and my own junk as well.

The debian package build process works in non-controlled directories.
It copies everything from the source tree, builds, and then installs
stuff into a chrooted area, which becomes the package.  So basically,
it just needs to copy less, or possibly use a non-default build
directory.

-- 
Matt Lewis