Home » Archived » IMP » Known problem: Need to run LPG manually to get IMP DSLs to build the first time
| Known problem: Need to run LPG manually to get IMP DSLs to build the first time [message #12398] |
Sun, 21 October 2007 16:26  |
 Stan Sutton
Messages: 121
Registered: July 2009 |
Senior Member |
|
|
Hi All,
This is a concern for those of you who have checked out the IMP projects
from CVS and are trying to get them to build. (It should not affect
those of you who have just installed the IMP features from the update
site and are trying to use IMP to build an IDE.)
In general, in order to get the IMP projects to build, you will need to
follow the instructions on the "IMP Developer's Corner" web page:
http://eclipse-imp.sourceforge.net/developers/index.html
One particular thing that you need to do is addressed there under the
heading "Building Required Parsers."
In the IMP CVS repository we don't usually store generated files that
can be regenerated in the user's workspace. This saves on storage space
and download/upload time. In particular, we don't store the generated
parsers and AST node types for the various languages that are part of
IMP. There are about half a dozen of these languages now, including the
LPG grammar specification language and various DSLs for specifying
things about an IMP IDE. The generated classes need to be regenerated
whenever an IMP projects that contains one of these languages is checked
out into a workspace.
Ideally, the LPG builder, which is part of the IMP installation, will
run automatically to regenerate the needed classes. However, there is a
problem in that the LPG builder does not seem to run automatically on a
project until after LPG has been run manually on the project. So, for
now, the IMP developer needs to manually run LPG on the grammar files
for each of these languages in order to get the containing projects to
build for the first time. The instructions on how to do this are
contained in the web page cited above.
(Note that the user must run LPG the first time as an "external tool."
After that the internal builder should work automatically.)
We have to go through this process ourselves, so we know that it's a bit
of a pain. We apologize for that, and we're working to fix it.
Regards,
Stan Sutton
|
|
|
| Re: Known problem: Need to run LPG manually to get IMP DSLs to build the first time [message #14741 is a reply to message #12398] |
Tue, 30 October 2007 21:31  |
Stan Sutton
Messages: 121
Registered: July 2009 |
Senior Member |
|
|
I believe that I've found and fixed this problem. I'm not sure when the
fix might show up in a release on the update site, but it's checked in
to the CVS repository. The affected class is
org.eclipse.imp.lpg.builder.LPGBuilder in project
org.eclipse.imp.lpg.runtime.
With this fix you should find that the LPG builder runs automatically
and successfully when you check out a project that contains some LPG
grammar files. Previously it was running automatically, just not
successfully :-)
Please let me know if you have any further problems with this. If
you're not checking out the code from the CVS repository but just
working with the release, until that's updated you can still work around
the problem by manually running LPG as an external tool as described below.
Regards,
Stan Sutton
Stanley Sutton wrote:
> Hi All,
>
> This is a concern for those of you who have checked out the IMP projects
> from CVS and are trying to get them to build. (It should not affect
> those of you who have just installed the IMP features from the update
> site and are trying to use IMP to build an IDE.)
>
> In general, in order to get the IMP projects to build, you will need to
> follow the instructions on the "IMP Developer's Corner" web page:
> http://eclipse-imp.sourceforge.net/developers/index.html
> One particular thing that you need to do is addressed there under the
> heading "Building Required Parsers."
>
> In the IMP CVS repository we don't usually store generated files that
> can be regenerated in the user's workspace. This saves on storage space
> and download/upload time. In particular, we don't store the generated
> parsers and AST node types for the various languages that are part of
> IMP. There are about half a dozen of these languages now, including the
> LPG grammar specification language and various DSLs for specifying
> things about an IMP IDE. The generated classes need to be regenerated
> whenever an IMP projects that contains one of these languages is checked
> out into a workspace.
>
> Ideally, the LPG builder, which is part of the IMP installation, will
> run automatically to regenerate the needed classes. However, there is a
> problem in that the LPG builder does not seem to run automatically on a
> project until after LPG has been run manually on the project. So, for
> now, the IMP developer needs to manually run LPG on the grammar files
> for each of these languages in order to get the containing projects to
> build for the first time. The instructions on how to do this are
> contained in the web page cited above.
>
> (Note that the user must run LPG the first time as an "external tool."
> After that the internal builder should work automatically.)
>
> We have to go through this process ourselves, so we know that it's a bit
> of a pain. We apologize for that, and we're working to fix it.
>
> Regards,
>
> Stan Sutton
|
|
|
| Re: Known problem: Need to run LPG manually to get IMP DSLs to build the first time [message #568766 is a reply to message #12398] |
Tue, 30 October 2007 21:31 |
Stan Sutton
Messages: 121
Registered: July 2009 |
Senior Member |
|
|
I believe that I've found and fixed this problem. I'm not sure when the
fix might show up in a release on the update site, but it's checked in
to the CVS repository. The affected class is
org.eclipse.imp.lpg.builder.LPGBuilder in project
org.eclipse.imp.lpg.runtime.
With this fix you should find that the LPG builder runs automatically
and successfully when you check out a project that contains some LPG
grammar files. Previously it was running automatically, just not
successfully :-)
Please let me know if you have any further problems with this. If
you're not checking out the code from the CVS repository but just
working with the release, until that's updated you can still work around
the problem by manually running LPG as an external tool as described below.
Regards,
Stan Sutton
Stanley Sutton wrote:
> Hi All,
>
> This is a concern for those of you who have checked out the IMP projects
> from CVS and are trying to get them to build. (It should not affect
> those of you who have just installed the IMP features from the update
> site and are trying to use IMP to build an IDE.)
>
> In general, in order to get the IMP projects to build, you will need to
> follow the instructions on the "IMP Developer's Corner" web page:
> http://eclipse-imp.sourceforge.net/developers/index.html
> One particular thing that you need to do is addressed there under the
> heading "Building Required Parsers."
>
> In the IMP CVS repository we don't usually store generated files that
> can be regenerated in the user's workspace. This saves on storage space
> and download/upload time. In particular, we don't store the generated
> parsers and AST node types for the various languages that are part of
> IMP. There are about half a dozen of these languages now, including the
> LPG grammar specification language and various DSLs for specifying
> things about an IMP IDE. The generated classes need to be regenerated
> whenever an IMP projects that contains one of these languages is checked
> out into a workspace.
>
> Ideally, the LPG builder, which is part of the IMP installation, will
> run automatically to regenerate the needed classes. However, there is a
> problem in that the LPG builder does not seem to run automatically on a
> project until after LPG has been run manually on the project. So, for
> now, the IMP developer needs to manually run LPG on the grammar files
> for each of these languages in order to get the containing projects to
> build for the first time. The instructions on how to do this are
> contained in the web page cited above.
>
> (Note that the user must run LPG the first time as an "external tool."
> After that the internal builder should work automatically.)
>
> We have to go through this process ourselves, so we know that it's a bit
> of a pain. We apologize for that, and we're working to fix it.
>
> Regards,
>
> Stan Sutton
|
|
|
Goto Forum:
Current Time: Wed Apr 24 16:11:29 GMT 2024
Powered by FUDForum. Page generated in 0.03508 seconds |
] 
Search
Help
Register
Login
Home
