[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tycho-user] How to build plugin-based products with platform-specific fragments?
|
We have feature-based products with lots of native code to compile into fragments. Our aggregator has profiles like linux-repo and win-repo and the reactor includes all the plugins (host plugins, fragment plugins, test plugins) and a special platform-specific projects for a feature and a repository. These platform builds only enable the tycho-platform-configuration environment that they're building. So at the end of this reactor each platform build machine has a P2 repo of the native fragments. We copy the windows fragment p2 repo to the linux machine, then build a profile that includes those platform-fragment p2 repos and the reactor has our shippable features and products. And this feature/product reactor has all tycho-platform-configuration environments enabled.
It means we're duplicating the compilation of the Java code on each platform but I couldn't see an easy way to avoid that.
-----Original Message-----
From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Christian Schulz
Sent: Wednesday, March 20, 2013 8:15 AM
To: tycho-user@xxxxxxxxxxx
Subject: Re: [tycho-user] How to build plugin-based products with platform-specific fragments?
Hello,
now I have switched to a feature based product, but now I am facing the same problem.
The platform-specific fragments are missing.
I had setted up the environments like described in my previous mail.
What is going wrong?
Cheers,
Chris
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
----------------------------------------------------------------------
This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.
