Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » OS X Cocoa x86_64 binary build
OS X Cocoa x86_64 binary build [message #488959] Wed, 30 September 2009 21:29 Go to next message
Bob Walker is currently offline Bob Walker
Messages: 31
Registered: July 2009
Member
I'm trying to build a x86_64 cocoa Application bundle using Hudson/Buckminster and I'm running into a problem. This is on an x86 Windows box. I don't believe Hudson is to blame, as I've extracted and tested at the command line with the same result.

Running the following command:

java -Dbuckminster.output.root=/D:/Data/JavaBuilds/Hudson/jobs/MyManager/workspace/arch/x86_64/os/macosx/ws/cocoa/\buckminster.output -Dbuckminster.temp.root=/D:/Data/JavaBuilds/Hudson/jobs/MyManager/workspace/arch/x86_64/os/macosx/ws/cocoa/\buckminster.temp -Dtarget.os=macosx -Dtarget.ws=cocoa -Dtarget.arch=x86_64 -jar  plugins\org.eclipse.equinox.launcher_1.0.200.v20090520.jar -application org.eclipse.buckminster.cmdline.headless -data /D:/Data/JavaBuilds/Hudson/jobs/MyManager/workspace/arch/x86_64/os/macosx/ws/cocoa/ --loglevel debug -S D:\Data\JavaBuilds\Hudson\jobs\MyManager\configurations\axis-arch\x86_64\axis-os\macosx\axis-ws\cocoa\builds\2009-09-30_14-19-17\commands.txt


in which commands.txt contains:

setpref targetPlatformPath="D:\\Data\\JavaBuilds\\Hudson\\jobs\\MyManagerPlatformCreation\\builds\\2009-09-27_12-40-45\\archive\\targetPlatform"
resolve "D:\\Data\\JavaBuilds\\Hudson\\jobs\\MyManager\\workspace\\my.manager.product.releng\\developer.cquery"
perform my.manager.product.feature#create.product.zip


leads to this error:

java.io.FileNotFoundException: C:\DOCUME~1\build\LOCALS~1\Temp\p2.brandingIron8797209790153527839\Eclipse.app\Contents\MacOS\MyManager (The system cannot find the path specified)
        at java.io.FileInputStream.open(Native Method)
        at java.io.FileInputStream.<init>(FileInputStream.java:106)
        at org.eclipse.equinox.internal.p2.core.helpers.FileUtils.zipFile(FileUtils.java:357)
        at org.eclipse.equinox.internal.p2.core.helpers.FileUtils.zip(FileUtils.java:286)
        at org.eclipse.equinox.internal.p2.core.helpers.FileUtils.zip(FileUtils.java:251)
        at org.eclipse.equinox.p2.publisher.AbstractPublisherAction.publishArtifact(AbstractPublisherAction.java:479)
        at org.eclipse.equinox.p2.publisher.eclipse.EquinoxExecutableAction.publishExecutableIU(EquinoxExecutableAction.java:122)
        at org.eclipse.equinox.p2.publisher.eclipse.EquinoxExecutableAction.perform(EquinoxExecutableAction.java:65)
        at org.eclipse.equinox.p2.publisher.eclipse.ApplicationLauncherAction.perform(ApplicationLauncherAction.java:66)
        at org.eclipse.equinox.p2.publisher.eclipse.ProductAction.perform(ProductAction.java:92)
        at org.eclipse.buckminster.pde.tasks.ProductAction.perform(ProductAction.java:137)
        at org.eclipse.equinox.p2.publisher.Publisher.publish(Publisher.java:172)
        at org.eclipse.buckminster.pde.tasks.P2SiteGenerator.run(P2SiteGenerator.java:321)
        at org.eclipse.buckminster.pde.tasks.P2SiteGenerator.internalPerform(P2SiteGenerator.java:427)
        at org.eclipse.buckminster.core.actor.AbstractActor.perform(AbstractActor.java:201)
        at org.eclipse.buckminster.core.internal.actor.PerformManager.perform(PerformManager.java:361)
        at org.eclipse.buckminster.core.internal.actor.PerformManager.perform(PerformManager.java:405)
        at org.eclipse.buckminster.core.commands.Perform.internalRun(Perform.java:118)
        at org.eclipse.buckminster.core.commands.WorkspaceCommand.run(WorkspaceCommand.java:191)
        at org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(AbstractCommand.java:155)
        at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:341)
        at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:135)
        at org.eclipse.buckminster.cmdline.Headless.start(Headless.java:189)
        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
        at org.eclipse.equinox.launcher.Main.main(Main.java:1287)


which in turn leaves this output log:


!SESSION 2009-09-30 14:20:45.899 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_13
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments:  -application org.eclipse.equinox.p2.director -artifactRepository file:/D:/Data/JavaBuilds/Hudson/jobs/MyManager/workspace/arch/x86_64/os/macosx/ws/cocoa/buckminster.output/my.manager.product.feature_1.0.0-eclipse.feature/site.p2/ -metadataRepository file:/D:/Data/JavaBuilds/Hudson/jobs/MyManager/workspace/arch/x86_64/os/macosx/ws/cocoa/buckminster.output/my.manager.product.feature_1.0.0-eclipse.feature/site.p2/ -destination D:\Data\JavaBuilds\Hudson\jobs\MyManager\workspace\arch\x86_64\os\macosx\ws\cocoa\buckminster.output\my.manager.product.feature_1.0.0-eclipse.feature\MyManager -bundlepool D:\Data\JavaBuilds\Hudson\jobs\MyManager\workspace\arch\x86_64\os\macosx\ws\cocoa\buckminster.output\my.manager.product.feature_1.0.0-eclipse.feature\MyManager -profile MyManagerProfile -profileProperties org.eclipse.update.install.features=true -installIU my.manager.product -p2.os macosx -p2.ws cocoa -p2.arch x86_64
Command-line arguments:  -application org.eclipse.equinox.p2.director -artifactRepository file:/D:/Data/JavaBuilds/Hudson/jobs/MyManager/workspace/arch/x86_64/os/macosx/ws/cocoa/buckminster.output/my.manager.product.feature_1.0.0-eclipse.feature/site.p2/ -metadataRepository file:/D:/Data/JavaBuilds/Hudson/jobs/MyManager/workspace/arch/x86_64/os/macosx/ws/cocoa/buckminster.output/my.manager.product.feature_1.0.0-eclipse.feature/site.p2/ -destination D:\Data\JavaBuilds\Hudson\jobs\MyManager\workspace\arch\x86_64\os\macosx\ws\cocoa\buckminster.output\my.manager.product.feature_1.0.0-eclipse.feature\MyManager -bundlepool D:\Data\JavaBuilds\Hudson\jobs\MyManager\workspace\arch\x86_64\os\macosx\ws\cocoa\buckminster.output\my.manager.product.feature_1.0.0-eclipse.feature\MyManager -profile MyManagerProfile -profileProperties org.eclipse.update.install.features=true -installIU my.manager.product -p2.os macosx -p2.ws cocoa -p2.arch x86_64 -consoleLog

!ENTRY org.eclipse.equinox.p2.engine 4 4 2009-09-30 14:21:04.211
!MESSAGE An error occurred while collecting items to be installed
!SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2009-09-30 14:21:04.211
!MESSAGE session context was:(profile=MyManagerProfile, phase=org.eclipse.equinox.internal.provisional.p2.engine.phases.Collect, operand=, action=).
!SUBENTRY 1 org.eclipse.equinox.p2.artifact.repository 4 0 2009-09-30 14:21:04.211
!MESSAGE No repository found containing: binary,my.manager.product.executable.cocoa.macosx.x86_64,0.0.1


I'm fairly happy that my target platform is setup correctly - it contains:
D:\Data\JavaBuilds\Hudson\jobs\MyManagerPlatformCreation\builds\2009-09-27_12-40-45\archive\targetPlatform\features\org.eclipse.equinox.executable_3.3.200.R35x_v20090724-7M-FneFF9aMTyz0pw04ONXn\bin\cocoa\macosx\x86_64\Eclipse.app


The only thing I notice that's odd is that the error refers to this:
my.manager.product.executable.cocoa.macosx.x86_64
where I would have expected this:
org.eclipse.equinox.executable.cocoa.macosx.x86_64


Is this a bug or have I misconfigured something somewhere? The commands were generated from my multi-config Hudson setup, but as I mentioned, I get the same results at the command line.

Thanks!

Bob Walker
Re: OS X Cocoa x86_64 binary build [message #489017 is a reply to message #488959] Thu, 01 October 2009 08:54 Go to previous messageGo to next message
Carsten Reckord is currently offline Carsten Reckord
Messages: 139
Registered: July 2009
Senior Member
Hi Bob,

I had the same problem a while ago. It is caused by a bug in the p2 "branding iron", which is responsible for creating a version of the
launcher branded with your product details (custom name etc.). The information what the original launcher is renamed to is not passed to the
caller of the branding process and thus a wrong path gets included in the packaging
(IIRC
C:\DOCUME~1\build\LOCALS~1\Temp\p2.brandingIron8797209790153 527839\Eclipse.app\Contents\MacOS\MyManager
should be
C:\DOCUME~1\build\LOCALS~1\Temp\p2.brandingIron8797209790153 527839\MyManager.app\Contents\MacOS\MyManager)

I have posted the issue on the equinox newsgroup, but haven't gotten an answer. Maybe a bug report would've been better...

(In my case, I found a workaround, but I guess that doesn't apply to you. Our RCP is really only a very small - and rather unchanging -
core, into which we install everything else, so I built the Mac RCP through the UI Wizards and used that in the further Hudson build)


Best regards,
Carsten

On 30.09.2009 23:29, Bob Walker wrote:
> I'm trying to build a x86_64 cocoa Application bundle using Hudson/Buckminster and I'm running into a problem. This is on an x86 Windows box. I don't believe Hudson is to blame, as I've extracted and tested at the command line with the same result.
>
> Running the following command:
>
> java -Dbuckminster.output.root=/D:/Data/JavaBuilds/Hudson/jobs/My Manager/workspace/arch/x86_64/os/macosx/ws/cocoa/\buckminste r.output -Dbuckminster.temp.root=/D:/Data/JavaBuilds/Hudson/jobs/MyMa nager/workspace/arch/x86_64/os/macosx/ws/cocoa/\buckminster. temp -Dtarget.os=macosx -Dtarget.ws=cocoa -Dtarget.arch=x86_64 -jar plugins\org.eclipse.equinox.launcher_1.0.200.v20090520.jar -application org.eclipse.buckminster.cmdline.headless -data /D:/Data/JavaBuilds/Hudson/jobs/MyManager/workspace/arch/x86 _64/os/macosx/ws/cocoa/ --loglevel debug -S D:\Data\JavaBuilds\Hudson\jobs\MyManager\configurations\axis -arch\x86_64\axis-os\macosx\axis-ws\cocoa\builds\2009-09-30_ 14-19-17\commands.txt
>
> in which commands.txt contains:
>
>
> setpref targetPlatformPath=" D:\\Data\\JavaBuilds\\Hudson\\jobs\\MyManagerPlatformCreatio n\\builds\\2009-09-27_12-40-45\\archive\\targetPlatform "
> resolve " D:\\Data\\JavaBuilds\\Hudson\\jobs\\MyManager\\workspace\\my .manager.product.releng\\developer.cquery "
> perform my.manager.product.feature#create.product.zip
>
>
> leads to this error:
>
>
> java.io.FileNotFoundException: C:\DOCUME~1\build\LOCALS~1\Temp\p2.brandingIron8797209790153 527839\Eclipse.app\Contents\MacOS\MyManager (The system cannot find the path specified)
> at java.io.FileInputStream.open(Native Method)
> at java.io.FileInputStream.<init>(FileInputStream.java:106)
> at org.eclipse.equinox.internal.p2.core.helpers.FileUtils.zipFi le(FileUtils.java:357)
> at org.eclipse.equinox.internal.p2.core.helpers.FileUtils.zip(F ileUtils.java:286)
> at org.eclipse.equinox.internal.p2.core.helpers.FileUtils.zip(F ileUtils.java:251)
> at org.eclipse.equinox.p2.publisher.AbstractPublisherAction.pub lishArtifact(AbstractPublisherAction.java:479)
> at org.eclipse.equinox.p2.publisher.eclipse.EquinoxExecutableAc tion.publishExecutableIU(EquinoxExecutableAction.java:122)
> at org.eclipse.equinox.p2.publisher.eclipse.EquinoxExecutableAc tion.perform(EquinoxExecutableAction.java:65)
> at org.eclipse.equinox.p2.publisher.eclipse.ApplicationLauncher Action.perform(ApplicationLauncherAction.java:66)
> at org.eclipse.equinox.p2.publisher.eclipse.ProductAction.perfo rm(ProductAction.java:92)
> at org.eclipse.buckminster.pde.tasks.ProductAction.perform(Prod uctAction.java:137)
> at org.eclipse.equinox.p2.publisher.Publisher.publish(Publisher .java:172)
> at org.eclipse.buckminster.pde.tasks.P2SiteGenerator.run(P2Site Generator.java:321)
> at org.eclipse.buckminster.pde.tasks.P2SiteGenerator.internalPe rform(P2SiteGenerator.java:427)
> at org.eclipse.buckminster.core.actor.AbstractActor.perform(Abs tractActor.java:201)
> at org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:361)
> at org.eclipse.buckminster.core.internal.actor.PerformManager.p erform(PerformManager.java:405)
> at org.eclipse.buckminster.core.commands.Perform.internalRun(Pe rform.java:118)
> at org.eclipse.buckminster.core.commands.WorkspaceCommand.run(W orkspaceCommand.java:191)
> at org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:155)
> at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:3 41)
> at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:1 35)
> at org.eclipse.buckminster.cmdline.Headless.start(Headless.java :189)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
>
>
> which in turn leaves this output log:
>
>
>
> !SESSION 2009-09-30 14:20:45.899 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.6.0_13
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
> Framework arguments: -application org.eclipse.equinox.p2.director -artifactRepository file:/D:/Data/JavaBuilds/Hudson/jobs/MyManager/workspace/arc h/x86_64/os/macosx/ws/cocoa/buckminster.output/my.manager.pr oduct.feature_1.0.0-eclipse.feature/site.p2/ -metadataRepository file:/D:/Data/JavaBuilds/Hudson/jobs/MyManager/workspace/arc h/x86_64/os/macosx/ws/cocoa/buckminster.output/my.manager.pr oduct.feature_1.0.0-eclipse.feature/site.p2/ -destination D:\Data\JavaBuilds\Hudson\jobs\MyManager\workspace\arch\x86_ 64\os\macosx\ws\cocoa\buckminster.output\my.manager.product. feature_1.0.0-eclipse.feature\MyManager -bundlepool D:\Data\JavaBuilds\Hudson\jobs\MyManager\workspace\arch\x86_ 64\os\macosx\ws\cocoa\buckminster.output\my.manager.product. feature_1.0.0-eclipse.feature\MyManager -profile MyManagerProfile -profileProperties org.eclipse.update.install.features=true -installIU my.manager.product -p2.os macosx -p2.ws cocoa -p2.arch x86_64
> Command-line arguments: -application org.eclipse.equinox.p2.director -artifactRepository file:/D:/Data/JavaBuilds/Hudson/jobs/MyManager/workspace/arc h/x86_64/os/macosx/ws/cocoa/buckminster.output/my.manager.pr oduct.feature_1.0.0-eclipse.feature/site.p2/ -metadataRepository file:/D:/Data/JavaBuilds/Hudson/jobs/MyManager/workspace/arc h/x86_64/os/macosx/ws/cocoa/buckminster.output/my.manager.pr oduct.feature_1.0.0-eclipse.feature/site.p2/ -destination D:\Data\JavaBuilds\Hudson\jobs\MyManager\workspace\arch\x86_ 64\os\macosx\ws\cocoa\buckminster.output\my.manager.product. feature_1.0.0-eclipse.feature\MyManager -bundlepool D:\Data\JavaBuilds\Hudson\jobs\MyManager\workspace\arch\x86_ 64\os\macosx\ws\cocoa\buckminster.output\my.manager.product. feature_1.0.0-eclipse.feature\MyManager -profile MyManagerProfile -profileProperties org.eclipse.update.install.features=true -installIU my.manager.product -p2.os macosx -p2.ws cocoa -p2.arch x86_64 -consoleLog
>
> !ENTRY org.eclipse.equinox.p2.engine 4 4 2009-09-30 14:21:04.211
> !MESSAGE An error occurred while collecting items to be installed
> !SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2009-09-30 14:21:04.211
> !MESSAGE session context was:(profile=MyManagerProfile, phase=org.eclipse.equinox.internal.provisional.p2.engine.pha ses.Collect, operand=, action=).
> !SUBENTRY 1 org.eclipse.equinox.p2.artifact.repository 4 0 2009-09-30 14:21:04.211
> !MESSAGE No repository found containing: binary,my.manager.product.executable.cocoa.macosx.x86_64,0.0 .1
>
>
> I'm fairly happy that my target platform is setup correctly - it contains:
> D:\Data\JavaBuilds\Hudson\jobs\MyManagerPlatformCreation\bui lds\2009-09-27_12-40-45\archive\targetPlatform\features\org. eclipse.equinox.executable_3.3.200.R35x_v20090724-7M-FneFF9a MTyz0pw04ONXn\bin\cocoa\macosx\x86_64\Eclipse.app
>
> The only thing I notice that's odd is that the error refers to this:
> my.manager.product.executable.cocoa.macosx.x86_64 where I would have expected this: org.eclipse.equinox.executable.cocoa.macosx.x86_64
>
> Is this a bug or have I misconfigured something somewhere? The commands were generated from my multi-config Hudson setup, but as I mentioned, I get the same results at the command line.
>
> Thanks!
>
> Bob Walker
Re: OS X Cocoa x86_64 binary build [message #489129 is a reply to message #488959] Thu, 01 October 2009 15:10 Go to previous messageGo to next message
Bob Walker is currently offline Bob Walker
Messages: 31
Registered: July 2009
Member
Thanks Carsten, appreciate the response!

That's good news, I'm glad it's not just me. I've filed a bug:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=291045

All the best,

Bob
Re: OS X Cocoa x86_64 binary build [message #514352 is a reply to message #489129] Sun, 14 February 2010 23:19 Go to previous messageGo to next message
Lauri Kimmel is currently offline Lauri Kimmel
Messages: 4
Registered: February 2010
Junior Member
I'm stuck at same point. Can't build OS X versions of RCP application using Hudson and headless Buckminster (3.5).
Any news on this issue?
Re: OS X Cocoa x86_64 binary build [message #514374 is a reply to message #514352] Mon, 15 February 2010 06:32 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
Can you please try 3.6 and see if the issue remains?

Thanks,
Thomas Hallgren

On 02/15/2010 12:19 AM, Lauri Kimmel wrote:
> I'm stuck at same point. Can't build OS X versions of RCP application
> using Hudson and headless Buckminster (3.5).
> Any news on this issue?
Re: OS X Cocoa x86_64 binary build [message #514602 is a reply to message #514374] Mon, 15 February 2010 22:49 Go to previous messageGo to next message
Lauri Kimmel is currently offline Lauri Kimmel
Messages: 4
Registered: February 2010
Junior Member
Installed 3.6 and subclipse feature from cloudsmith update site

$ ./director/director -r http://download.eclipse.org/tools/buckminster/headless-3.6/ -d ./buckminster -p Buckminster -i org.eclipse.buckminster.cmdline.product
$ ./buckminster/buckminster install http://download.eclipse.org/tools/buckminster/headless-3.6/ org.eclipse.buckminster.core.headless.feature
$ ./buckminster/buckminster install http://download.eclipse.org/tools/buckminster/headless-3.6/ org.eclipse.buckminster.cvs.headless.feature
$ ./buckminster/buckminster install http://download.eclipse.org/tools/buckminster/headless-3.6/ org.eclipse.buckminster.pde.headless.feature
$ ./buckminster/buckminster install http://download.eclipse.org/tools/buckminster/headless-3.6/ org.eclipse.buckminster.maven.headless.feature
$ ./buckminster/buckminster install http://download.cloudsmith.com/buckminster/external/ org.eclipse.buckminster.subclipse.headless.feature


Materializing my project failed with error message

ERROR   [0001] : java.lang.NoSuchMethodError: org.eclipse.buckminster.core.resolver.NodeQuery.getRevision()J


Looks same as NoSuchMethodError with current 3.6 build.
Re: OS X Cocoa x86_64 binary build [message #514609 is a reply to message #514602] Mon, 15 February 2010 23:08 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
Please use our http://download.cloudsmith.com/buckminster/external-3.6 site for Subclipse.

See http://www.eclipse.org/forums/index.php?t=msg&th=162592& amp;start=0& for more info.

Regards,
Thomas Hallgren


On 02/15/2010 11:49 PM, Lauri Kimmel wrote:
> Installed 3.6 and subclipse feature from cloudsmith update site
>
>
> $ ./director/director -r
> http://download.eclipse.org/tools/buckminster/headless-3.6/ -d
> ./buckminster -p Buckminster -i org.eclipse.buckminster.cmdline.product
> $ ./buckminster/buckminster install
> http://download.eclipse.org/tools/buckminster/headless-3.6/
> org.eclipse.buckminster.core.headless.feature
> $ ./buckminster/buckminster install
> http://download.eclipse.org/tools/buckminster/headless-3.6/
> org.eclipse.buckminster.cvs.headless.feature
> $ ./buckminster/buckminster install
> http://download.eclipse.org/tools/buckminster/headless-3.6/
> org.eclipse.buckminster.pde.headless.feature
> $ ./buckminster/buckminster install
> http://download.eclipse.org/tools/buckminster/headless-3.6/
> org.eclipse.buckminster.maven.headless.feature
> $ ./buckminster/buckminster install
> http://download.cloudsmith.com/buckminster/external/
> org.eclipse.buckminster.subclipse.headless.feature
>
>
> Materializing my project failed with error message
>
> ERROR [0001] : java.lang.NoSuchMethodError:
> org.eclipse.buckminster.core.resolver.NodeQuery.getRevision( )J
>
>
> Looks same as
> http://www.eclipse.org/forums/index.php?t=msg&th=160657& amp;start=0&
Re: OS X Cocoa x86_64 binary build [message #514612 is a reply to message #514609] Tue, 16 February 2010 00:07 Go to previous messageGo to next message
Lauri Kimmel is currently offline Lauri Kimmel
Messages: 4
Registered: February 2010
Junior Member
Thanks for the Subclipse hint. Materialization is ok now.

The p2 "branding iron" bug is still present. Ends with same message as usual

!MESSAGE No repository found containing: binary,my.app.product.executable.cocoa.macosx.x86_64
Re: OS X Cocoa x86_64 binary build [message #534268 is a reply to message #514612] Tue, 18 May 2010 14:32 Go to previous messageGo to next message
Andreas Pakulat is currently offline Andreas Pakulat
Messages: 15
Registered: July 2009
Junior Member
Just posted a separate item for the same topic, didn't find this before...

This has been lying around for almost 3 months, what do you guys (who need to build RCP apps on MacOSX with Buckminster) do currently? Does anybody have a workaround, besides building the rcp app manually?

I'd really like to get off our old, barely-working, build-solution and migrate to hudson, but that won't work without being able to build Mac packages.
Re: OS X Cocoa x86_64 binary build [message #534311 is a reply to message #534268] Tue, 18 May 2010 15:22 Go to previous messageGo to next message
Carsten Reckord is currently offline Carsten Reckord
Messages: 139
Registered: July 2009
Senior Member
Hi Andreas,

I have split my RCP build into building a core product, basically just a bare-bones RCP environment with a bit of branding, and installing
our features into that. I did this to have separate updatable units for our features on the "Installation Details" page, but it has the nice
side effect of providing a simple workaround for the Mac issue:

I just build the minimal Mac RCP in my IDE through the standard PDE mechanism and use that for the (rest of the) Mac build on Hudson. Since
it is so barebone it rarely ever changes and the amount of manual work is really neglectible.

Cheers,
Carsten


On 18.05.2010 16:32, Andreas Pakulat wrote:
> Just posted a separate item for the same topic, didn't find this before...
>
> This has been lying around for almost 3 months, what do you guys (who need to build RCP apps on MacOSX with Buckminster) do currently? Does anybody have a workaround, besides building the rcp app manually?
>
> I'd really like to get off our old, barely-working, build-solution and migrate to hudson, but that won't work without being able to build Mac packages.
Re: OS X Cocoa x86_64 binary build [message #544136 is a reply to message #488959] Thu, 01 July 2010 17:11 Go to previous messageGo to next message
Scott Anderson is currently offline Scott Anderson
Messages: 2
Registered: July 2009
Junior Member
I found that forcing our CI server to only use build agents that have a case insensitive filesystem (windows/mac) will avoid the defect in the branding code. It is a work-around for us right now.
Re: OS X Cocoa x86_64 binary build [message #544141 is a reply to message #544136] Thu, 01 July 2010 17:47 Go to previous message
Henrik Lindberg is currently offline Henrik Lindberg
Messages: 2500
Registered: July 2009
Senior Member
Good to know about that workaround. Thanks for sharing.
- henrik
On 7/1/10 7:11 PM, Scott Anderson wrote:
> I found that forcing our CI server to only use build agents that have a
> case insensitive filesystem (windows/mac) will avoid the defect in the
> branding code. It is a work-around for us right now.
Previous Topic:qualifier substitution with revision number
Next Topic:Format of target.os, target.ws, target.arch if not *
Goto Forum:
  


Current Time: Mon Sep 22 22:31:37 GMT 2014

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

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