The C files in the tarball are generated from some ATS source. You need
GTK±2.0 and libgc to compile it:
make all_ported
I encourage you to give it a try.
My ATS source uses some ATS library code that are yet not publicly
available. However, the generated C
code can be compiled as long as ATS-includes and ATS-contrib-includes are
available. While this is anticipated,
seeing it as a reality is still quite exciting
The C files in the tarball are generated from some ATS source. You need
GTK±2.0 and libgc to compile it:
make all_ported
I encourage you to give it a try.
My ATS source uses some ATS library code that are yet not publicly
available. However, the generated C
code can be compiled as long as ATS-includes and ATS-contrib-includes
are available. While this is anticipated,
seeing it as a reality is still quite exciting
The C files in the tarball are generated from some ATS source. You need
GTK±2.0 and libgc to compile it:
make all_ported
I encourage you to give it a try.
My ATS source uses some ATS library code that are yet not publicly
available. However, the generated C
code can be compiled as long as ATS-includes and ATS-contrib-includes are
available. While this is anticipated,
seeing it as a reality is still quite exciting
The C files in the tarball are generated from some ATS source. You need
GTK±2.0 and libgc to compile it:
make all_ported
I encourage you to give it a try.
My ATS source uses some ATS library code that are yet not publicly
available. However, the generated C
code can be compiled as long as ATS-includes and ATS-contrib-includes are
available. While this is anticipated,
seeing it as a reality is still quite exciting