]
seb win commented on JBIDE-2720:
--------------------------------
Hi,
I faced the same issue I used process explorer and found that it was using the one located
in c:\windows\System32 I have an other one in c:\windows\SysWOW64 i assume that eclipse
should use the last one but I don't know how to configure it. Can you please help ?
Many thnaks
Need 64-bit windows support
---------------------------
Key: JBIDE-2720
URL:
https://issues.jboss.org/browse/JBIDE-2720
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: visual-page-editor-core
Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
Reporter: Samuel Mendenhall
Assignee: Yahor Radtsevich
Fix For: 4.1.x
Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log,
buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt,
build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1,
mozconfig2, vpe-win-jdk64.png
If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load.
We should look into providing a xulrunner for Windows 64-bit.
*Update:*
In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is
provided via experimental update site:
http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr...
{color:red}*Known problems:*{color}
* XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK
*If you get [R6034
error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...]
you may:*
* Try to uninstall Intel OpenCL SDK
* *OR* Disable XULRunner by adding the option
{{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or
{{jbdevstudio.ini}} if you use JBoss Developer Studio)
If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will
very appreciate if you run Process Explorer as described in [this
comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...]
and help us to find conflicting library.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: