1. Cross Platform
Hi All, in particular core developers
Is it feasible, and what would be involved with providing a facility for the
interpreter to output a bound executable for another platform?
In particular, I would be interested in building a windows executable on a Linux
platform, using exu to generate a windows .exe
It strikes me that since bind(u/w) attaches .il code to a back end it shouldn't
matter which backend it actually gets attached to?
Gary
2. Re: Cross Platform
Gary Shingles wrote:
>
> Hi All, in particular core developers
>
> Is it feasible, and what would be involved with providing a facility for the
> interpreter to output a bound executable for another platform?
>
> In particular, I would be interested in building a windows executable on a
> Linux
> platform, using exu to generate a windows .exe
>
> It strikes me that since bind(u/w) attaches .il code to a back end it
> shouldn't
> matter which backend it actually gets attached to?
>
> Gary
If you succeed in making a Windows .exe file using GNU/Linux,
you would still need to go to Windows (or use something like wine)
to test the .exe file. So you can't do without Windows (or wine, etc.)
if you want to make something that works on Windows.
3. Re: Cross Platform
Gary Shingles wrote:
> Hi All, in particular core developers
>
> Is it feasible, and what would be involved with providing a facility for the
> interpreter to output a bound executable for another platform?
>
> In particular, I would be interested in building a windows executable on a
> Linux
> platform, using exu to generate a windows .exe
>
> It strikes me that since bind(u/w) attaches .il code to a back end it
> shouldn't
> matter which backend it actually gets attached to?
This is similar to a previous cross-platform question
about the Translator. It amounts to "tricking" Euphoria
into thinking it is running on a different platform.
I haven't tested any of this, but something like
the following might work for the Binder as well:
http://www.openeuphoria.org/cgi-bin/esearch.exu?fromMonth=8&fromYear=C&toMonth=8&toYear=C&postedBy=rds&keywords=global.e
However I think the demand for this is so low,
that you'll have to experiment with this yourself.
Maybe we could eventually add a command-line option
to specify the platform.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
4. Re: Cross Platform
Jerry Story wrote:
> > In particular, I would be interested in building a windows executable on a
> > Linux
> > platform, using exu to generate a windows .exe
> >
> > It strikes me that since bind(u/w) attaches .il code to a back end it
> > shouldn't
> > matter which backend it actually gets attached to?
>
> If you succeed in making a Windows .exe file using GNU/Linux,
> you would still need to go to Windows (or use something like wine)
> to test the .exe file. So you can't do without Windows (or wine, etc.)
> if you want to make something that works on Windows.
Hi Jerry
I'm not really thinking about a 'testing' situation, more like a customised
program that is known to compile and work OK, with maybe just a few changes in
pre-defined variables.
Eg, a program on a web site that generates an executable on demand (from a Linux
host :)
Gary
5. Re: Cross Platform
Robert Craig wrote:
> I haven't tested any of this, but something like
> the following might work for the Binder as well:
>
> <a
> href="http://www.openeuphoria.org/cgi-bin/esearch.exu?fromMonth=8&fromYear=C&toMonth=8&toYear=C&postedBy=rds&keywords=global.e">http://www.openeuphoria.org/cgi-bin/esearch.exu?fromMonth=8&fromYear=C&toMonth=8&toYear=C&postedBy=rds&keywords=global.e</a>
>
> However I think the demand for this is so low,
> that you'll have to experiment with this yourself.
Thanks Rob, I'll check this out.
Gary
