Eclipse RCP, upgrading from x32 to x64 platform: Automatic build still looks for x32 launcher plugin

Question

I'm upgrading an RCP from x32 to x64.

I'm able to export the product from within Eclipse without any issues but when I try to export it via my automatic build it doesn't work and gives me the following error:

Eclipse_3_7_64Bit\plugins\org.eclipse.pde.build_3.7.0.v20111116-2009\scripts\productBuild\productBuild.xml:69: Unable to find plug-in: org.eclipse.equinox.launcher.win32.win32.x86_0.0.0. Please check the error log for more details.

As far as I understand the build is looking for the x32 version of the plugin when it should instead look for the x64 version.

I also read here that I should add this

--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.100.v20110502

Either I did something wrong or it doesn't work.

This is the command I use to start the build (Works fine for x32 builds):

""%JavaHome%\bin\java" -jar "%ECLIPSE_LOCATION%\plugins\org.eclipse.equinox.launcher_1.2.0.v20110502.jar" -application org.eclipse.ant.core.antRunner -f "%BUILD_SOURCE%\com.company.myproduct.rcp.setup\scripts\build.xml""

Note that I search replaced company and product information!

Build.xml

productBuild.xml

allElements.xml

build.properties

# Version of org.ecilpse.pdebuild
pdeBuildPluginVersion=3.7.0.v20111116-2009


# Version of org.eclipse.equinox.launcher
equinoxLauncherPluginVersion=1.2.0.v20110502

# ProductVersion
productVersion=00.00Test0

############# BASE LOCATION #########################
#
# Specify the directory of the base under which your
# your build target is located. This directory should
# contain the RCP Runtime Binary that you want to 
# compile against.
#
#####################################################

base=//server/Eclipse/Eclipse_3_7_64Bit

############# ECLIPSE LOCATION ######################
#
# Specify the directory of the Eclipse installation
# that will be used to execute PDE Build.
#
#####################################################

eclipseLocation=//server/Eclipse/Eclipse_3_7_64Bit

############# PRODUCT/PACKAGING CONTROL #############
product=/ com.mytest.myproduct.rcp/myProduct.product
runPackager=false

#Set the name of the archive that will result from the product build.
#archiveNamePrefix=

# The prefix that will be used in the generated archive.
archivePrefix=MyProduct

# The location underwhich all of the build output will be collected.
collectingFolder=${archivePrefix}

# The list of {os, ws, arch} configurations to build.  This 
# value is a '&' separated list of ',' separate triples.  For example, 
#     configs=win32,win32,x86 & linux,motif,x86
# By default the value is *,*,*
#configs = *, *, *
configs=win32,win32,x86_64
##& \
#   linux, gtk, ppc &\
# linux, gtk, x86 & \
#   linux, gtk, x86_64 & \
#   linux, motif, x86 & \
#   solaris, motif, sparc & \
#   solaris, gtk, sparc & \
#   aix, motif, ppc & \
#   hpux, motif, PA_RISC & \
#   macosx, carbon, ppc

# By default PDE creates one archive (result) per entry listed in the configs property.
# Setting this value to try will cause PDE to only create one output containing all 
# artifacts for all the platforms listed in the configs property.
#groupConfigurations=true

#The format of the archive. By default a zip is created using antZip.
#The list can only contain the configuration for which the desired format is different than zip.
#archivesFormat=win32, win32, x86 - antZip& \
#   linux, gtk, ppc - antZip &\
#    linux, gtk, x86 - antZip& \
#   linux, gtk, x86_64 - antZip& \
# linux, motif, x86 - antZip& \
#   solaris, motif, sparc - antZip& \
#   solaris, gtk, sparc - antZip& \
#   aix, motif, ppc - antZip& \
#   hpux, motif, PA_RISC - antZip& \
#   macosx, carbon, ppc - antZip

#Set to true if you want the output to be ready for an update jar (no site.xml generated)
#outputUpdateJars = false

#Set to true for Jnlp generation
#codebase should be a URL that will be used as the root of all relative URLs in the output.
#generateJnlp=false
#jnlp.codebase=
#jnlp.j2se=
#jnlp.locale=
#jnlp.generateOfflineAllowed=true or false generate  attribute in the generated features
#jnlp.configs=${configs}            #uncomment to filter the content of the generated jnlp files based on the configuration being built

#Set to true if you want to sign jars
#signJars=false
#sign.alias=
#sign.keystore=
#sign.storepass=

#Arguments to send to the zip executable
zipargs=

#Arguments to send to the tar executable
tarargs=

#Control the creation of a file containing the version included in each configuration - on by default 
generateVersionsLists=false

############## BUILD NAMING CONTROL ################
# The directory into which the build elements are fetched and where
# the build takes place.
buildDirectory=D:/ccviews/.MyProduct2_CR_0065098_Dev/Java/build_00.00Test0

# Type of build.  Used in naming the build output.  Typically this value is
# one of I, N, M, S, ...
buildType=R

# ID of the build.  Used in naming the build output.
buildId=MyProductbuild

# Label for the build.  Used in naming the build output
buildLabel=build_output

# Timestamp for the build.  Used in naming the build output
timestamp=007

#The value to be used for the qualifier of a plugin or feature when you want to override the value computed by pde.
#The value will only be applied to plugin or features indicating build.properties, qualifier = context 
#forceContextQualifier=Testi

#Enable / disable the generation of a suffix for the features that use .qualifier. 
#The generated suffix is computed according to the content of the feature   
#generateFeatureVersionSuffix=true

############# BASE CONTROL #############
# Settings for the base Eclipse components and Java class libraries 
# against which you are building.
# Base location for anything the build needs to compile against.  For example,
# in most RCP app or a plug-in,  the baseLocation should be the location of a previously
# installed Eclipse against which the application or plug-in code will be compiled and the RCP delta pack.

baseLocation=${eclipseLocation}
#Os/Ws/Arch/nl of the eclipse specified by baseLocation
baseos=win32
basews=win32
basearch=x86

#this property indicates whether you want the set of plug-ins and features to be considered during the build to be limited to the ones reachable from the features / plugins being built
filteredDependencyCheck=false

#pluginPath is a list of locations in which to find plugins and features.  This list is separated by the platform file separator (; or :)
#a location is one of:  
#- the location of the jar or folder that is the plugin or feature : /path/to/foo.jar or /path/to/foo
#- a directory that contains a /plugins or /features subdirectory
#- the location of a feature.xml, or for 2.1 style plugins, the plugin.xml or fragment.xml
#pluginPath=

skipBase=true
eclipseURL=
eclipseBuildId=
eclipseBaseURL=${eclipseURL}/eclipse-platform-${eclipseBuildId}-win32.zip


############# MAP FILE CONTROL ################
# This section defines CVS tags to use when fetching the map files from the repository.
# If you want to fetch the map file from repository / location, change the getMapFiles target in the customTargets.xml

skipMaps=true
mapsRepo=:pserver:anonymous@example.com/path/to/repo
mapsRoot=path/to/maps
mapsCheckoutTag=HEAD

#tagMaps=true
mapsTagTag=v${buildId}


############ REPOSITORY CONTROL ###############
# This section defines properties parameterizing the repositories where plugins, fragments
# bundles and features are being obtained from. 

# The tags to use when fetching elements to build.
# By default thebuilder will use whatever is in the maps.  
# This value takes the form of a comma separated list of repository identifier (like used in the map files) and the 
# overriding value
# For example fetchTag=CVS=HEAD, SVN=v20050101
# fetchTag=HEAD
skipFetch=true


############# JAVA COMPILER OPTIONS ##############
# The location of the Java jars to compile against.  Typically the rt.jar for your JDK/JRE
#bootclasspath=${java.home}/lib/rt.jar

# specific JRE locations to compile against. These values are used to compile bundles specifying a 
# Bundle-RequiredExecutionEnvironment. Uncomment and set values for environments that you support
#CDC-1.0/Foundation-1.0= /path/to/rt.jar
#CDC-1.1/Foundation-1.1=
#OSGi/Minimum-1.0=
#OSGi/Minimum-1.1=
#JRE-1.1=
#J2SE-1.2=
#J2SE-1.3=
#J2SE-1.4=
#J2SE-1.5=
#JavaSE-1.6=
#PersonalJava-1.1=
#PersonalJava-1.2=
#CDC-1.0/PersonalBasis-1.0=
#CDC-1.0/PersonalJava-1.0=
#CDC-1.1/PersonalBasis-1.1=
#CDC-1.1/PersonalJava-1.1=

# Specify the output format of the compiler log when eclipse jdt is used
logExtension=.log

# Whether or not to include debug info in the output jars
javacDebugInfo=false 

# Whether or not to fail the build if there are compiler errors
javacFailOnError=true

# Enable or disable verbose mode of the compiler
javacVerbose=true

# Extra arguments for the compiler. These are specific to the java compiler being used.
#compilerArg=

# Default value for the version of the source code. This value is used when compiling plug-ins that do not set the Bundle-RequiredExecutionEnvironment or set javacSource in build.properties
javacSource=1.6

# Default value for the version of the byte code targeted. This value is used when compiling plug-ins that do not set the Bundle-RequiredExecutionEnvironment or set javacTarget in build.properties.
javacTarget=1.6

greg-449 · Accepted Answer

The line

configs=win32, win32, x86

in your build properties specifies a Windows 32 bit build ('x86' means 32 bit).

Use

configs=win32, win32, x86_64

for 64 bit ('x86_64').

You will also need to specify a 64 bit Eclipse in the configuration.

Eclipse RCP, upgrading from x32 to x64 platform: Automatic build still looks for x32 launcher plugin

Answers (1)

Related Questions