[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [mdt-ocl.dev] LPG support
|
Hi
The five (cloned to 6) LPG executables are now in the build plugin.
[The classic support can be adjusted once the build plugin is promoted
to non-examples.]
The "Generate LPG *" launches in ewillink/ocl25 use them to produce LPG
variants of the four Xtext grammars. They are all LALR(1) and conflict free.
Only trivial changes were needed once the QVTo transformations were
debugged.
'::*' rather than '::' '*' for the tail of an import
a couple of keywords migrated from restricted to reserved.
There is only untested action code for the lexers. What does the parser
action code need to do to join up nicely to the automated CS2AS
functionality? Probably like Xtext, it must install a CS proxy for each
reference. Perhaps this proxy can be coupled more directly avoiding the
complexities of URI lookup.
Regards
Ed Willink
On 10/10/2014 13:36, Adolfo Sanchez-Barbudo Herrera wrote:
Hi
Which users ? This shouldn't be used by end users, just very
occasionally (classic code fixes) by you and perhaps by me.
Resuming, no better ideas but I'd not melt the brain with this, even a
simple README/HOW_TO should suffice for us.
Regards,
Adolfo.
On 08/10/2014 15:16, Ed Willink wrote:
Hi
Just tried running LPG. Failed since I now only have win32-x86-x64
machines.
LPG seems to have stabilized; 2.0.23 is 3 years old. 2.0.20 is announced
as the latest. We still use 2.0.17.
There is no 64 bit Windows distribution but the 32 bit one works fine.
Just need to clone lpg.generator.win32-x86 as
lpg.generator.win32-x86-x64 and rename the internal lpg.exe similarly.
This isn't very user friendly and developing, documenting and
integrating a custom installation script seems hardly justified.
Waiting for LPG to support 64 bit Windows may take a long time so
suggest:
Copy all lpg.exe's into our build plugin, allowing a suitable rename for
64 bit Windows. This will also avoid users having to close all the
unwanted LPG fragments that give errors on the 'wrong' platform.
Any better ideas?
Regards
Ed Willink
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4765 / Virus Database: 4040/8358 - Release Date: 10/10/14