| Different eclipse.exe results in "eclipse executable launcher was unable to locate its companio [message #535758] |
Tue, 25 May 2010 10:03  |
Eclipse User |
|
|
|
hi!
I'm not sure whether this is a buckminster issue in the first place, but here is our problem:
we set up a standard buckminster build and when we run it from within the IDE (installed buckminster is 1.1.350) we get a working output.
if we run the same build from our hudson server (installed buckminster is 1.2.360) we also get an output, but when we try to start the application we get the error "eclipse executable launcher was unable to locate its companion shared library". we noticed, that the eclipse.exe of that package has a different filesize compared to the eclipse.exe of the working output. if we simply replace it with the eclipse.exe from the working build of our local buckminster this application starts as well.
has anyone had this problem before?
regards,
Andreas
|
|
|
|
|
| Re: Different eclipse.exe results in "eclipse executable launcher was unable to locate its comp [message #535907 is a reply to message #535893] |
Wed, 26 May 2010 05:56  |
| Eclipse User |
|
|
|
Hi Andreas,
>
> well, you're totally right. the buildserver is running a 32bit windows
> xp, while my working desktop machine is a 64bit windows xp.
> but shouldn't it still work running the 32bit build in a 64bit environment?
>
Only in case you are using a 32 Bit VM on the 64 Bit system. Can you try
the build product on a 32 bit system to confirm if that is the cause?
If it works there, you should probably set the target.arch on the build
server to 64 Bit and give that a try.
Best regards,
Johannes
|
|
|
Powered by
FUDForum. Page generated in 0.03449 seconds
Home