Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EPP » A product form multiple platforms
A product form multiple platforms [message #486390] Thu, 17 September 2009 13:44 Go to next message
Rudolf Hornig is currently offline Rudolf HornigFriend
Messages: 12
Registered: July 2009
Junior Member
Hello we are building our own product based on eclipse, cdt,
gef, emf and on our own feature. The final requirement is that
we want to put the product into a single archive file, BUT
that archive file must support win32/linux32/64 and mac os. In
pre p2 times, i have just created the builds for different
architectures and copied the results into a single directory
(taking into the account that the launcher binaries should not
overwrite each other. This approach is no longer working of
course (and it's very hackish...)

My question is: what is the recommended way to create a
product (in a single archive file) which can be run on
multiple platforms (of course starting with different
launchers)... Can somebody enlighten ma or give some pointer
how to do this?

Thanks, Rudolf
Re: A product form multiple platforms [message #486884 is a reply to message #486390] Sun, 20 September 2009 17:55 Go to previous messageGo to next message
David Williams is currently offline David WilliamsFriend
Messages: 176
Registered: July 2009
Senior Member
Rudolf Hornig wrote:
> Hello we are building our own product based on eclipse, cdt,
> gef, emf and on our own feature. The final requirement is that
> we want to put the product into a single archive file, BUT
> that archive file must support win32/linux32/64 and mac os. In
> pre p2 times, i have just created the builds for different
> architectures and copied the results into a single directory
> (taking into the account that the launcher binaries should not
> overwrite each other. This approach is no longer working of
> course (and it's very hackish...)
>
> My question is: what is the recommended way to create a
> product (in a single archive file) which can be run on
> multiple platforms (of course starting with different
> launchers)... Can somebody enlighten ma or give some pointer
> how to do this?
>
> Thanks, Rudolf
>

Someone from this packaging newsgroup might happen to know the answer,
but I'd suggest you ask on eclipse.platform newsgroup (which I've added
to CC in in my reply) as readers there might be more familiar with
general packaging issues.

While not obvious, this packaging newsgroup doesn't really deal with
general packaging issues, but some specific ones related to yearly release.
Re: A product form multiple platforms [message #486886 is a reply to message #486884] Sun, 20 September 2009 17:57 Go to previous messageGo to next message
David Williams is currently offline David WilliamsFriend
Messages: 176
Registered: July 2009
Senior Member
David Williams wrote:
> Rudolf Hornig wrote:
>> Hello we are building our own product based on eclipse, cdt, gef, emf
>> and on our own feature. The final requirement is that we want to put
>> the product into a single archive file, BUT that archive file must
>> support win32/linux32/64 and mac os. In pre p2 times, i have just
>> created the builds for different architectures and copied the results
>> into a single directory (taking into the account that the launcher
>> binaries should not overwrite each other. This approach is no longer
>> working of course (and it's very hackish...)
>>
>> My question is: what is the recommended way to create a product (in a
>> single archive file) which can be run on multiple platforms (of course
>> starting with different launchers)... Can somebody enlighten ma or
>> give some pointer how to do this?
>>
>> Thanks, Rudolf
>>
>
> Someone from this packaging newsgroup might happen to know the answer,
> but I'd suggest you ask on eclipse.platform newsgroup (which I've added
> to CC in in my reply) as readers there might be more familiar with
> general packaging issues.
>
> While not obvious, this packaging newsgroup doesn't really deal with
> general packaging issues, but some specific ones related to yearly release.

Whoops, forgot to add eclipse.platform as I said I would.
Re: A product form multiple platforms [message #487188 is a reply to message #486886] Tue, 22 September 2009 11:44 Go to previous messageGo to next message
Rudolf Hornig is currently offline Rudolf HornigFriend
Messages: 12
Registered: July 2009
Junior Member
Has anyone in this group an idea about the question below?
Thanks, Rudolf

>>> Hello we are building our own product based on eclipse, cdt, gef, emf
>>> and on our own feature. The final requirement is that we want to put
>>> the product into a single archive file, BUT that archive file must
>>> support win32/linux32/64 and mac os. In pre p2 times, i have just
>>> created the builds for different architectures and copied the results
>>> into a single directory (taking into the account that the launcher
>>> binaries should not overwrite each other. This approach is no longer
>>> working of course (and it's very hackish...)
>>>
>>> My question is: what is the recommended way to create a product (in a
>>> single archive file) which can be run on multiple platforms (of course
>>> starting with different launchers)... Can somebody enlighten ma or
>>> give some pointer how to do this?
>>>
>>> Thanks, Rudolf
>>>
>>
>> Someone from this packaging newsgroup might happen to know the answer,
>> but I'd suggest you ask on eclipse.platform newsgroup (which I've added
>> to CC in in my reply) as readers there might be more familiar with
>> general packaging issues.
>>
>> While not obvious, this packaging newsgroup doesn't really deal with
>> general packaging issues, but some specific ones related to yearly
>> release.
>
> Whoops, forgot to add eclipse.platform as I said I would.
Re: A product form multiple platforms [message #487619 is a reply to message #487188] Wed, 23 September 2009 18:35 Go to previous messageGo to next message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
The problem is that p2 can only manage and install for one particular
platform at a time.

The simplest way I can see to do this is to have a separate
configuration area and separate p2 profile per platform.

You would do 4 installations, each to a separate location, using the
same bundle pool, and the same p2 data area, but different p2 profile
ids. The bundle pool can be in the normal eclipse root, and each
install can be a sub folder:
/eclipse/plugins
/features
/p2/*
/win32/configuration/*
/eclipse.exe
/eclipse.ini
/linux32/configuration/*
/eclipse
/eclipse.ini

p2 views this as two separate installs that share a common pool of
plugins (each selecting a different subset of plugins from the pool).
The biggest issue is that when you are running and choose to install
something or update, then only the running platform gets updated, and
you need to repeat the operation on the other platform.

I'm not sure the details of the director calls to do this using the 3.5
org.eclipse.equinox.p2.director application. But PDE/Build still uses
the older org.eclipse.equinox.p2.director.app.application. If you look
at org.eclipse.pde.build/scripts/genericTargets.xml runDirector you can
set the p2.director.installPath, p2.director.dataArea, and
p2.director.bundlepool independently of each other.

-Andrew

Rudolf Hornig wrote:
> Has anyone in this group an idea about the question below?
> Thanks, Rudolf
>
>>>> Hello we are building our own product based on eclipse, cdt, gef, emf
>>>> and on our own feature. The final requirement is that we want to put
>>>> the product into a single archive file, BUT that archive file must
>>>> support win32/linux32/64 and mac os. In pre p2 times, i have just
>>>> created the builds for different architectures and copied the results
>>>> into a single directory (taking into the account that the launcher
>>>> binaries should not overwrite each other. This approach is no longer
>>>> working of course (and it's very hackish...)
>>>>
>>>> My question is: what is the recommended way to create a product (in a
>>>> single archive file) which can be run on multiple platforms (of course
>>>> starting with different launchers)... Can somebody enlighten ma or
>>>> give some pointer how to do this?
>>>>
>>>> Thanks, Rudolf
>>>>
>>> Someone from this packaging newsgroup might happen to know the answer,
>>> but I'd suggest you ask on eclipse.platform newsgroup (which I've added
>>> to CC in in my reply) as readers there might be more familiar with
>>> general packaging issues.
>>>
>>> While not obvious, this packaging newsgroup doesn't really deal with
>>> general packaging issues, but some specific ones related to yearly
>>> release.
>> Whoops, forgot to add eclipse.platform as I said I would.
>
>
Re: A product form multiple platforms [message #489105 is a reply to message #487619] Thu, 01 October 2009 14:13 Go to previous message
Rudolf Hornig is currently offline Rudolf HornigFriend
Messages: 12
Registered: July 2009
Junior Member
Andrew Niefer wrote:

Thanks a lot for your answer...

> The problem is that p2 can only manage and install for one particular
> platform at a time.

Yes I have figured that out, but this is not a big problem, because our
users do not run the same install under several platforms at the same time.
We just want to create a single zip file which is runnable on different
platforms. So this is fortunately not an issue.

>
> The simplest way I can see to do this is to have a separate
> configuration area and separate p2 profile per platform.
>
> You would do 4 installations, each to a separate location, using the
> same bundle pool, and the same p2 data area, but different p2 profile
> ids. The bundle pool can be in the normal eclipse root, and each
> install can be a sub folder:
> /eclipse/plugins
> /features
> /p2/*
> /win32/configuration/*
> /eclipse.exe
> /eclipse.ini
> /linux32/configuration/*
> /eclipse
> /eclipse.ini
>
> p2 views this as two separate installs that share a common pool of
> plugins (each selecting a different subset of plugins from the pool).
> The biggest issue is that when you are running and choose to install
> something or update, then only the running platform gets updated, and
> you need to repeat the operation on the other platform.

This is almost exactly what I have chosen to do with the exception that I
have a separate p2 area for each platform (and used the same profile id).
The update issue is not a problem, because users are using only a single
platform at a time. We just wanted to distribute in a single TGZ file which
can e extracted on any platform.

>
> I'm not sure the details of the director calls to do this using the 3.5
> org.eclipse.equinox.p2.director application. But PDE/Build still uses
> the older org.eclipse.equinox.p2.director.app.application. If you look
> at org.eclipse.pde.build/scripts/genericTargets.xml runDirector you can
> set the p2.director.installPath, p2.director.dataArea, and
> p2.director.bundlepool independently of each other.

Thanks a lot, this is really helpful. I have not found this part of code,
but I will experiment with it. At the end I have resorted to create the
proposed directory structure manually and modified the ini files by hand to
point the installation area (-install), but I will experiment with the
directory application and will try to use your recommendation to actually
install everything as you have suggested...

Now I know at least, that I'm on the right track...
Thanks, Rudolf

>
> -Andrew
>
> Rudolf Hornig wrote:
>> Has anyone in this group an idea about the question below?
>> Thanks, Rudolf
>>
>>>>> Hello we are building our own product based on eclipse, cdt, gef, emf
>>>>> and on our own feature. The final requirement is that we want to put
>>>>> the product into a single archive file, BUT that archive file must
>>>>> support win32/linux32/64 and mac os. In pre p2 times, i have just
>>>>> created the builds for different architectures and copied the results
>>>>> into a single directory (taking into the account that the launcher
>>>>> binaries should not overwrite each other. This approach is no longer
>>>>> working of course (and it's very hackish...)
>>>>>
>>>>> My question is: what is the recommended way to create a product (in a
>>>>> single archive file) which can be run on multiple platforms (of course
>>>>> starting with different launchers)... Can somebody enlighten ma or
>>>>> give some pointer how to do this?
>>>>>
>>>>> Thanks, Rudolf
>>>>>
>>>> Someone from this packaging newsgroup might happen to know the answer,
>>>> but I'd suggest you ask on eclipse.platform newsgroup (which I've added
>>>> to CC in in my reply) as readers there might be more familiar with
>>>> general packaging issues.
>>>>
>>>> While not obvious, this packaging newsgroup doesn't really deal with
>>>> general packaging issues, but some specific ones related to yearly
>>>> release.
>>> Whoops, forgot to add eclipse.platform as I said I would.
>>
>>
Re: A product form multiple platforms [message #579842 is a reply to message #486390] Sun, 20 September 2009 17:55 Go to previous message
David Williams is currently offline David WilliamsFriend
Messages: 176
Registered: July 2009
Senior Member
Rudolf Hornig wrote:
> Hello we are building our own product based on eclipse, cdt,
> gef, emf and on our own feature. The final requirement is that
> we want to put the product into a single archive file, BUT
> that archive file must support win32/linux32/64 and mac os. In
> pre p2 times, i have just created the builds for different
> architectures and copied the results into a single directory
> (taking into the account that the launcher binaries should not
> overwrite each other. This approach is no longer working of
> course (and it's very hackish...)
>
> My question is: what is the recommended way to create a
> product (in a single archive file) which can be run on
> multiple platforms (of course starting with different
> launchers)... Can somebody enlighten ma or give some pointer
> how to do this?
>
> Thanks, Rudolf
>

Someone from this packaging newsgroup might happen to know the answer,
but I'd suggest you ask on eclipse.platform newsgroup (which I've added
to CC in in my reply) as readers there might be more familiar with
general packaging issues.

While not obvious, this packaging newsgroup doesn't really deal with
general packaging issues, but some specific ones related to yearly release.
Re: A product form multiple platforms [message #579870 is a reply to message #486884] Sun, 20 September 2009 17:57 Go to previous message
David Williams is currently offline David WilliamsFriend
Messages: 176
Registered: July 2009
Senior Member
David Williams wrote:
> Rudolf Hornig wrote:
>> Hello we are building our own product based on eclipse, cdt, gef, emf
>> and on our own feature. The final requirement is that we want to put
>> the product into a single archive file, BUT that archive file must
>> support win32/linux32/64 and mac os. In pre p2 times, i have just
>> created the builds for different architectures and copied the results
>> into a single directory (taking into the account that the launcher
>> binaries should not overwrite each other. This approach is no longer
>> working of course (and it's very hackish...)
>>
>> My question is: what is the recommended way to create a product (in a
>> single archive file) which can be run on multiple platforms (of course
>> starting with different launchers)... Can somebody enlighten ma or
>> give some pointer how to do this?
>>
>> Thanks, Rudolf
>>
>
> Someone from this packaging newsgroup might happen to know the answer,
> but I'd suggest you ask on eclipse.platform newsgroup (which I've added
> to CC in in my reply) as readers there might be more familiar with
> general packaging issues.
>
> While not obvious, this packaging newsgroup doesn't really deal with
> general packaging issues, but some specific ones related to yearly release.

Whoops, forgot to add eclipse.platform as I said I would.
Re: A product form multiple platforms [message #579885 is a reply to message #486886] Tue, 22 September 2009 11:44 Go to previous message
Rudolf Hornig is currently offline Rudolf HornigFriend
Messages: 12
Registered: July 2009
Junior Member
Has anyone in this group an idea about the question below?
Thanks, Rudolf

>>> Hello we are building our own product based on eclipse, cdt, gef, emf
>>> and on our own feature. The final requirement is that we want to put
>>> the product into a single archive file, BUT that archive file must
>>> support win32/linux32/64 and mac os. In pre p2 times, i have just
>>> created the builds for different architectures and copied the results
>>> into a single directory (taking into the account that the launcher
>>> binaries should not overwrite each other. This approach is no longer
>>> working of course (and it's very hackish...)
>>>
>>> My question is: what is the recommended way to create a product (in a
>>> single archive file) which can be run on multiple platforms (of course
>>> starting with different launchers)... Can somebody enlighten ma or
>>> give some pointer how to do this?
>>>
>>> Thanks, Rudolf
>>>
>>
>> Someone from this packaging newsgroup might happen to know the answer,
>> but I'd suggest you ask on eclipse.platform newsgroup (which I've added
>> to CC in in my reply) as readers there might be more familiar with
>> general packaging issues.
>>
>> While not obvious, this packaging newsgroup doesn't really deal with
>> general packaging issues, but some specific ones related to yearly
>> release.
>
> Whoops, forgot to add eclipse.platform as I said I would.
Re: A product form multiple platforms [message #579901 is a reply to message #487188] Wed, 23 September 2009 18:35 Go to previous message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
The problem is that p2 can only manage and install for one particular
platform at a time.

The simplest way I can see to do this is to have a separate
configuration area and separate p2 profile per platform.

You would do 4 installations, each to a separate location, using the
same bundle pool, and the same p2 data area, but different p2 profile
ids. The bundle pool can be in the normal eclipse root, and each
install can be a sub folder:
/eclipse/plugins
/features
/p2/*
/win32/configuration/*
/eclipse.exe
/eclipse.ini
/linux32/configuration/*
/eclipse
/eclipse.ini

p2 views this as two separate installs that share a common pool of
plugins (each selecting a different subset of plugins from the pool).
The biggest issue is that when you are running and choose to install
something or update, then only the running platform gets updated, and
you need to repeat the operation on the other platform.

I'm not sure the details of the director calls to do this using the 3.5
org.eclipse.equinox.p2.director application. But PDE/Build still uses
the older org.eclipse.equinox.p2.director.app.application. If you look
at org.eclipse.pde.build/scripts/genericTargets.xml runDirector you can
set the p2.director.installPath, p2.director.dataArea, and
p2.director.bundlepool independently of each other.

-Andrew

Rudolf Hornig wrote:
> Has anyone in this group an idea about the question below?
> Thanks, Rudolf
>
>>>> Hello we are building our own product based on eclipse, cdt, gef, emf
>>>> and on our own feature. The final requirement is that we want to put
>>>> the product into a single archive file, BUT that archive file must
>>>> support win32/linux32/64 and mac os. In pre p2 times, i have just
>>>> created the builds for different architectures and copied the results
>>>> into a single directory (taking into the account that the launcher
>>>> binaries should not overwrite each other. This approach is no longer
>>>> working of course (and it's very hackish...)
>>>>
>>>> My question is: what is the recommended way to create a product (in a
>>>> single archive file) which can be run on multiple platforms (of course
>>>> starting with different launchers)... Can somebody enlighten ma or
>>>> give some pointer how to do this?
>>>>
>>>> Thanks, Rudolf
>>>>
>>> Someone from this packaging newsgroup might happen to know the answer,
>>> but I'd suggest you ask on eclipse.platform newsgroup (which I've added
>>> to CC in in my reply) as readers there might be more familiar with
>>> general packaging issues.
>>>
>>> While not obvious, this packaging newsgroup doesn't really deal with
>>> general packaging issues, but some specific ones related to yearly
>>> release.
>> Whoops, forgot to add eclipse.platform as I said I would.
>
>
Re: A product form multiple platforms [message #579943 is a reply to message #487619] Thu, 01 October 2009 14:13 Go to previous message
Rudolf Hornig is currently offline Rudolf HornigFriend
Messages: 12
Registered: July 2009
Junior Member
Andrew Niefer wrote:

Thanks a lot for your answer...

> The problem is that p2 can only manage and install for one particular
> platform at a time.

Yes I have figured that out, but this is not a big problem, because our
users do not run the same install under several platforms at the same time.
We just want to create a single zip file which is runnable on different
platforms. So this is fortunately not an issue.

>
> The simplest way I can see to do this is to have a separate
> configuration area and separate p2 profile per platform.
>
> You would do 4 installations, each to a separate location, using the
> same bundle pool, and the same p2 data area, but different p2 profile
> ids. The bundle pool can be in the normal eclipse root, and each
> install can be a sub folder:
> /eclipse/plugins
> /features
> /p2/*
> /win32/configuration/*
> /eclipse.exe
> /eclipse.ini
> /linux32/configuration/*
> /eclipse
> /eclipse.ini
>
> p2 views this as two separate installs that share a common pool of
> plugins (each selecting a different subset of plugins from the pool).
> The biggest issue is that when you are running and choose to install
> something or update, then only the running platform gets updated, and
> you need to repeat the operation on the other platform.

This is almost exactly what I have chosen to do with the exception that I
have a separate p2 area for each platform (and used the same profile id).
The update issue is not a problem, because users are using only a single
platform at a time. We just wanted to distribute in a single TGZ file which
can e extracted on any platform.

>
> I'm not sure the details of the director calls to do this using the 3.5
> org.eclipse.equinox.p2.director application. But PDE/Build still uses
> the older org.eclipse.equinox.p2.director.app.application. If you look
> at org.eclipse.pde.build/scripts/genericTargets.xml runDirector you can
> set the p2.director.installPath, p2.director.dataArea, and
> p2.director.bundlepool independently of each other.

Thanks a lot, this is really helpful. I have not found this part of code,
but I will experiment with it. At the end I have resorted to create the
proposed directory structure manually and modified the ini files by hand to
point the installation area (-install), but I will experiment with the
directory application and will try to use your recommendation to actually
install everything as you have suggested...

Now I know at least, that I'm on the right track...
Thanks, Rudolf

>
> -Andrew
>
> Rudolf Hornig wrote:
>> Has anyone in this group an idea about the question below?
>> Thanks, Rudolf
>>
>>>>> Hello we are building our own product based on eclipse, cdt, gef, emf
>>>>> and on our own feature. The final requirement is that we want to put
>>>>> the product into a single archive file, BUT that archive file must
>>>>> support win32/linux32/64 and mac os. In pre p2 times, i have just
>>>>> created the builds for different architectures and copied the results
>>>>> into a single directory (taking into the account that the launcher
>>>>> binaries should not overwrite each other. This approach is no longer
>>>>> working of course (and it's very hackish...)
>>>>>
>>>>> My question is: what is the recommended way to create a product (in a
>>>>> single archive file) which can be run on multiple platforms (of course
>>>>> starting with different launchers)... Can somebody enlighten ma or
>>>>> give some pointer how to do this?
>>>>>
>>>>> Thanks, Rudolf
>>>>>
>>>> Someone from this packaging newsgroup might happen to know the answer,
>>>> but I'd suggest you ask on eclipse.platform newsgroup (which I've added
>>>> to CC in in my reply) as readers there might be more familiar with
>>>> general packaging issues.
>>>>
>>>> While not obvious, this packaging newsgroup doesn't really deal with
>>>> general packaging issues, but some specific ones related to yearly
>>>> release.
>>> Whoops, forgot to add eclipse.platform as I said I would.
>>
>>
Previous Topic:Building a product
Next Topic:Building org.eclipse.epp.package.java
Goto Forum:
  


Current Time: Sun Dec 21 07:09:15 GMT 2014

Powered by FUDForum. Page generated in 0.26589 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software