[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cbi-dev] Bug 383538 - Disable natives repo
|
Ok, +1
Paul, Igor - are you both on support of this?
On 06/28/2012 11:45 AM, Aleksandar Kurtakov wrote:
----- Original Message -----
From: "Andrew Ross" <andrew.ross@xxxxxxxxxxx>
To: cbi-dev@xxxxxxxxxxx
Sent: Thursday, June 28, 2012 6:39:18 PM
Subject: Re: [cbi-dev] Bug 383538 - Disable natives repo
Hi Guys,
I agree.
However, before we make-it-so, I would like to understand
specifically
how it works when you don't actually build the natives? I can think
of a
variety of reasons one might not want to do so.
Natives are build only if one pass -Dnatives=<native>. If such parameter is not passed the natives will be resolved from e.g http://git.eclipse.org/c/platform/eclipse.platform.swt.binaries.git/ in the swt case as they would have proper pom.xml files and etc. instead of coping them from the native repo used now. This will remove the need for the current native repo to be recreated every time swt rebuilds its natives.
Alex
Andrew
On 06/28/2012 11:34 AM, Aleksandar Kurtakov wrote:
----- Original Message -----
From: "Thanh Ha" <thanh.ha@xxxxxxxxxxx>
To: "Common-build Developers discussion" <cbi-dev@xxxxxxxxxxx>
Sent: Thursday, June 28, 2012 6:22:58 PM
Subject: [cbi-dev] Bug 383538 - Disable natives repo
Hi Everyone,
I'm taking a look at Bug 383538 [1] regarding removing the natives
from the eclipse-parent pom. I've tested it and I'm able to build
cbi on linux, macosx, and windows just fine without natives now
(both with and without the -Dnative=<native> parameter).
Is there any reason we should keep the natives if we can build
successfully without it now? or should I go ahead and commit this
change?
I think that getting rid of it as soon as the modified poms are
merged into respective projects might be the best call.
Alex
Thanks,
Thanh
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=383538
