1. Missing source files ?
- Posted by Bernie Ryan <xotron at bluefrog.com> Oct 18, 2006
- 510 views
for Linux interpeter The imakeu file compiles a list of .c files that are not included in the source files example: backen.c, etc. Bernie My files in archive: WMOTOR, XMOTOR, W32ENGIN, MIXEDLIB, EU_ENGIN, WIN32ERU, WIN32API Can be downloaded here: http://www.rapideuphoria.com/cgi-bin/asearch.exu?dos=on&win=on&lnx=on&gen=on&keywords=bernie+ryan
2. Re: Missing source files ?
- Posted by Robert Craig <rds at RapidEuphoria.com> Oct 18, 2006
- 482 views
Bernie Ryan wrote: > for Linux interpeter > > The imakeu file compiles a list of .c files that are not included > in the source files example: backen.c, etc. Those files are generated by the Translator on the step before that. The interpreter front-end is written in Euphoria and is translated to a bunch of C files. Then, rather than using emake, imakeu compiles those front-end files and links them with the hand-written backend files, be_*.c. Any C files, that start with "be_" are hand-written back-end C files. Any other C files are probably generated by the Translator. Look at the top line. The build process is very incestuous In various places: - the interpreter is used to run the translator. - the translator is used to build the interpreter. - the translator is used to build the translator. Regards, Rob Craig Rapid Deployment Software http://www.RapidEuphoria.com
3. Re: Missing source files ?
- Posted by Bernie Ryan <xotron at bluefrog.com> Oct 18, 2006
- 490 views
Robert Craig wrote: > > Bernie Ryan wrote: > > for Linux interpeter > > > > The imakeu file compiles a list of .c files that are not included > > in the source files example: backen.c, etc. > > Those files are generated by the Translator on the step > before that. > > The interpreter front-end is written in Euphoria and > is translated to a bunch of C files. Then, rather than > using emake, imakeu compiles those front-end files and > links them with the hand-written backend files, be_*.c. > > Any C files, that start with "be_" are hand-written > back-end C files. Any other C files are probably > generated by the Translator. Look at the top line. > > The build process is very incestuous > In various places: > - the interpreter is used to run the translator. > - the translator is used to build the interpreter. > - the translator is used to build the translator. > > Regards, > Rob Craig > Rapid Deployment Software > <a href="http://www.RapidEuphoria.com">http://www.RapidEuphoria.com</a> Thanks, Rob Bernie My files in archive: WMOTOR, XMOTOR, W32ENGIN, MIXEDLIB, EU_ENGIN, WIN32ERU, WIN32API Can be downloaded here: http://www.rapideuphoria.com/cgi-bin/asearch.exu?dos=on&win=on&lnx=on&gen=on&keywords=bernie+ryan
4. Re: Missing source files ?
- Posted by "Greg Haberek" <ghaberek at gmail.com> Oct 18, 2006
- 507 views
> The build process is very incestuous > In various places: > - the interpreter is used to run the translator. > - the translator is used to build the interpreter. > - the translator is used to build the translator. Circular compilation. I love it. :) It almost sounds like The Chicken and The Egg, but at least we know the C-based interpreter came first. :) ~Greg