Eclipse Community Forums: Oomph » Build configuration with Oomph

Home » Eclipse Projects » Oomph » Build configuration with Oomph

Build configuration with Oomph [message #1712626]

Mon, 26 October 2015 18:18

Eclipse User

Hi everyone,

Is it possible to create a Build configuration with Setup Project Model? I created a build configuration using "External Tools Configurations" (that uses scons to build a project). Now, I would like to be able to export this configurations in my future Eclipse Installations.

I found "Projects Build" Task in a setup Project Model, but seems like this is something different, or may be I don't know how to use it properly.

Thank you!

Re: Build configuration with Oomph [message #1712680 is a reply to message #1712626]

Tue, 27 October 2015 09:15

Eclipse User

Artem,

We have a bunch of build configurations for Oomph itself, but we keep
them in the git repository (via the Common tab we place them in our
releng bundle) so they're always available when Oomph has been setup.
Isn't that sufficient in your case?

On 27/10/2015 1:48 PM, Artem Gritsenko wrote:
> Hi everyone,
>
> Is it possible to create a Build configuration with Setup Project
> Model? I created a build configuration using "External Tools
> Configurations" (that uses scons to build a project). Now, I would
> like to be able to export this configurations in my future Eclipse
> Installations.
> I found "Projects Build" Task in a setup Project Model, but seems like
> this is something different, or may be I don't know how to use it
> properly.
>
> Thank you!

Re: Build configuration with Oomph [message #1712727 is a reply to message #1712680]

Tue, 27 October 2015 13:19

Eclipse User

Hi Ed,

Thank you! This is something similar to what I am looking for. Though, I have two more questions:
1. How can I use the .launch file in my installation together with an existing .setup file?
2. Where can I lookup the existing keys/values for a .launch file? In particular, I am interested in adding environmental variables to my build configuration.

Artem

Re: Build configuration with Oomph [message #1712739 is a reply to message #1712727]

Tue, 27 October 2015 15:28

Eclipse User

Artem,

Laucher configurations too have a common tab that you can save them in a
project so they're always available. You can specify environment
variables in the Environment tab of the launch configuration. Oomph
also has a Launch task so you can launch a named launcher available in
one of your projects. This blog, which describes how to launch MWE
might be helpful if that's your goal:

http://www.lorenzobettini.it/2015/10/oomph-setup-for-xtext-projects/

On 27/10/2015 6:19 PM, Artem Gritsenko wrote:
> Hi Ed,
>
> Thank you! This is something similar to what I am looking for. Though,
> I have two more questions:
> 1. How can I use the .launch file in my installation together with an
> existing .setup file?
> 2. Where can I lookup the existing keys/values for a .launch file? In
> particular, I am interested in adding environmental variables to my
> build configuration.
>
> Artem

Re: Build configuration with Oomph [message #1712960 is a reply to message #1712739]

Thu, 29 October 2015 11:04

Eclipse User

Ed,

Thank you for your reply. The blog says that creating a launch task as simple as providing a path to .launch file that contains the build/debug configuration. I did that by setting up the "Launch Configuration" field of a Launch task to an absolute path of a launch file, but I don't see any build configurations after the installation. Can you give me a hint on what am I doing wrong?

Artem

Re: Build configuration with Oomph [message #1712966 is a reply to message #1712960]

Thu, 29 October 2015 12:22

Eclipse User

Am 29.10.2015 um 16:04 schrieb Artem Gritsenko:
> Ed,
>
> Thank you for your reply. The blog says that creating a launch task as simple as providing a path to .launch file that
> contains the build/debug configuration. I did that by setting up the "Launch Configuration" field of a Launch task to
> an absolute path of a launch file, but I don't see any build configurations after the installation. Can you give me a
> hint on what am I doing wrong?
I think you need to specify a workspace-relative path.

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Re: Build configuration with Oomph [message #1712968 is a reply to message #1712966]

Thu, 29 October 2015 12:37

Eclipse User

You just need to specify the name of the launcher. Look at his example:

https://raw.githubusercontent.com/LorenzoBettini/xsemantics/master/devtools/it.xsemantics.workspace/Xsemantics.setup

On 29/10/2015 5:22 PM, Eike Stepper wrote:
> Am 29.10.2015 um 16:04 schrieb Artem Gritsenko:
>> Ed,
>>
>> Thank you for your reply. The blog says that creating a launch task
>> as simple as providing a path to .launch file that contains the
>> build/debug configuration. I did that by setting up the "Launch
>> Configuration" field of a Launch task to an absolute path of a launch
>> file, but I don't see any build configurations after the
>> installation. Can you give me a hint on what am I doing wrong?
> I think you need to specify a workspace-relative path.
>
> Cheers
> /Eike
>
> ----
> http://www.esc-net.de
> http://thegordian.blogspot.com
> http://twitter.com/eikestepper
>
>

Re: Build configuration with Oomph [message #1713026 is a reply to message #1712968]

Thu, 29 October 2015 18:13

Eclipse User

HI Ed,

In this example, they assign "Generate Language Infrastructure (it.xsemantics.example.fjcached)" or "GenerateFJ.mwe2" in the "launcher" field. None of them looks like a relative/absolute path to a .launch file. Can you give more details on that? Is having only the .launch file enough or I need to create some Targlets or Component Extension tasks?

I attached the screenshot with the setting for my launch task.

Artem

Attachment: Screen Shot 2015-10-29 at 6.09.50 PM.png
(Size: 262.01KB, Downloaded 191 times)

Re: Build configuration with Oomph [message #1713033 is a reply to message #1713026]

Fri, 30 October 2015 00:07

Eclipse User

Artem,

None of them are the absolute or relative path. They specify just the
name of the launcher. I.e., the last segment of the path without the
file extension as you see it in the menus and in the Name: field of the
configuration dialogs. If the launcher depends on projects that must
be built first or on plugins in the target platform, you likely need a
build task first. The Xsemantics setup is in Oomph's Github project
catalog, so you can try out how it works.

On 29/10/2015 11:13 PM, Artem Gritsenko wrote:
> HI Ed,
>
> In this example, they assign "Generate Language Infrastructure (it.xsemantics.example.fjcached)" or "GenerateFJ.mwe2" in the "launcher" field. None of them looks like a relative/absolute path to a .launch file. Can you give more details on that? Is having only the .launch file enough or I need to create some Targlets or Component Extension tasks?
>
> I attached the screenshot with the setting for my launch task.
>
> Artem

Re: Build configuration with Oomph [message #1713038 is a reply to message #1713033]

Fri, 30 October 2015 03:36

Eclipse User

Ed is right: first ensure the project containing the .launch file has
been built. Afterwards you just specify the file name without the
..launch extension and it should work.

Axel

Am 30.10.2015 um 05:07 schrieb Ed Merks:
> Artem,
>
> None of them are the absolute or relative path. They specify just the
> name of the launcher. I.e., the last segment of the path without the
> file extension as you see it in the menus and in the Name: field of the
> configuration dialogs. If the launcher depends on projects that must
> be built first or on plugins in the target platform, you likely need a
> build task first. The Xsemantics setup is in Oomph's Github project
> catalog, so you can try out how it works.
>
>
> On 29/10/2015 11:13 PM, Artem Gritsenko wrote:
>> HI Ed,
>>
>> In this example, they assign "Generate Language Infrastructure
>> (it.xsemantics.example.fjcached)" or "GenerateFJ.mwe2" in the
>> "launcher" field. None of them looks like a relative/absolute path to
>> a .launch file. Can you give more details on that? Is having only the
>> .launch file enough or I need to create some Targlets or Component
>> Extension tasks?
>>
>> I attached the screenshot with the setting for my launch task.
>>
>> Artem
>

Re: Build configuration with Oomph [message #1713134 is a reply to message #1712960]

Sun, 01 November 2015 04:09

Eclipse User

On 29/10/2015 16:04, Artem Gritsenko wrote:
> Ed,
>
> Thank you for your reply. The blog says that creating a launch task as
> simple as providing a path to .launch file that contains the build/debug
> configuration. I did that by setting up the "Launch Configuration" field
> of a Launch task to an absolute path of a launch file, but I don't see
> any build configurations after the installation. Can you give me a hint
> on what am I doing wrong?
>
> Artem

Hi

The blog actually says

"For the “Launch” task, you need to use the name of the .launch file,
without .launch."

And as Ed said, you first need to ensure the project containing the
..launch is in the workspace... (if I remember correctly, the build task
is not required for the launch configuration to be found: it is required
for the mwe2 launcher class to be found.)

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book

Re: Build configuration with Oomph [message #1714104 is a reply to message #1713134]

Mon, 09 November 2015 17:40

Eclipse User

Thanks everyone, it works now.

Artem

Previous Topic:	How to display $Author$ in code template
Next Topic:	Eclipse installation Java version

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Nov 07 04:02:18 EST 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter