| Correct build setup with platform specific cdt fragments / unpacking fragments after installation [message #640134] |
Fri, 19 November 2010 09:36  |
 Stefan Schuster
Messages: 5
Registered: July 2009 |
Junior Member |
|
|
Hi all,
we develop an Eclipse based IDE for the computer algebra system
(Ap)CoCoA with integration of an external interactive interpreter (a
command line tool) for the three platforms win32, linux, macosx.
To enable sending of Ctrl-C to the interpreter, we make use of the CDT's
ProcessFactory.
The necessary CDT plugins and fragments are inluded in the 'Plug-ins and
Fragments' secion of our "main feature", and since on win32 the CDT
plug-in must be unpacked, we enabled the corresponding "Unpack the
plug-in archive after the installation" option.
We're doing headless builds on a linux machine for all platforms using
the antRunner application. So, our problem was, how to get the platform
specific CDT fragments and the build together.
The platform specific CDT parts are provided in different fragments and
thus is after installing CDT in Eclipse only the fragment for your
current platform available.
So, to get the CDT parts for all platforms, we downloaded the 'cdt
master package' from the CDT website and made it available to the build
by adding the path to 'pluginPath' in our 'build.properties', in
addition to the delta-pack path.
Now we have a question and a problem:
1) Our question: is this the correct way to include and compile against
the platform specific CDT parts?
2) Our problem: The win32 CDT fragment is not unpacked. Reading other
posts here we looked in the build repositories 'content.xml' and noted
the missing "<instruction key='zipped'> true </...>" entry. After adding
this, we can correctly update from the build repository on windows, but
still don't know, how to get the file unpacked during the build of the
product.
Thanks for your help.
With kind regards,
Stefan Schuster
|
|
|
| Re: Correct build setup with platform specific cdt fragments / unpacking fragments after installatio [message #640795 is a reply to message #640134] |
Tue, 23 November 2010 08:26  |
Stefan Schuster
Messages: 5
Registered: July 2009 |
Junior Member |
|
|
I think I found the answer: "Reusing p2 Metadata". Deleting cdt master
from 'pluginPath' and putting it inside a 'repoBaseLocation' along with
a 'transformedRepoLocation' resolved the problem.
Cheers,
Stefan
Am 11/19/10 10:36 AM, schrieb Stefan Schuster:
> Hi all,
>
> we develop an Eclipse based IDE for the computer algebra system
> (Ap)CoCoA with integration of an external interactive interpreter (a
> command line tool) for the three platforms win32, linux, macosx.
>
> To enable sending of Ctrl-C to the interpreter, we make use of the CDT's
> ProcessFactory.
>
> The necessary CDT plugins and fragments are inluded in the 'Plug-ins and
> Fragments' secion of our "main feature", and since on win32 the CDT
> plug-in must be unpacked, we enabled the corresponding "Unpack the
> plug-in archive after the installation" option.
>
> We're doing headless builds on a linux machine for all platforms using
> the antRunner application. So, our problem was, how to get the platform
> specific CDT fragments and the build together.
> The platform specific CDT parts are provided in different fragments and
> thus is after installing CDT in Eclipse only the fragment for your
> current platform available.
> So, to get the CDT parts for all platforms, we downloaded the 'cdt
> master package' from the CDT website and made it available to the build
> by adding the path to 'pluginPath' in our 'build.properties', in
> addition to the delta-pack path.
>
>
> Now we have a question and a problem:
>
> 1) Our question: is this the correct way to include and compile against
> the platform specific CDT parts?
>
> 2) Our problem: The win32 CDT fragment is not unpacked. Reading other
> posts here we looked in the build repositories 'content.xml' and noted
> the missing "<instruction key='zipped'> true </...>" entry. After adding
> this, we can correctly update from the build repository on windows, but
> still don't know, how to get the file unpacked during the build of the
> product.
>
> Thanks for your help.
>
> With kind regards,
> Stefan Schuster
|
|
|
Powered by
FUDForum. Page generated in 0.02766 seconds
] 
Search
Help
Register
Login
Home
