Native Development

[ahsan_iqbal]

Hi

I have compiled my application successfully but whenever I tried to debug it on Blackberry playbook it gave me following error

Error in final launch sequence
Cannot prepare and download the binary
Packaging failed:1
Error: Unable to resolve path variable "workspace_loc"

please help

Ahsan

[selom]

Hello Ahsan,

the error suggests that your environment variables or workspace/packaging configuration may be incorrect.

Can you please double check by right-clicking on the project, select Properties->Resource->Linked resources and confirming that the workspace_loc path is valid?

Cheers

Selom

[ahsan_iqbal]

Hi Selom

Thanx for your response, I have verified workspace_loc and its valid, what could be other reason.

please help

[ahsan_iqbal]

hi

here is the stacktrace of exception 

Error: Unable to resolve path variable "workspace_loc"
at com.qnx.tools.ide.bbt.debug.core.internal.launch.BBTLaunchUtils.prepareAndDownloadBinaries(BBTLaunchUtils.java:305)
at com.qnx.tools.ide.bbt.debug.ui.internal.launch.BBTDSFFinalLaunchSequence.stepPrepareAndDownloadBinariesRemote(BBTDSFFinalLaunchSequence.java:93)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.cdt.dsf.concurrent.ReflectionSequence$ReflectionStep.execute(ReflectionSequence.java:155)
at org.eclipse.cdt.dsf.concurrent.Sequence.executeStep(Sequence.java:452)
at org.eclipse.cdt.dsf.concurrent.Sequence.access$2(Sequence.java:366)
at org.eclipse.cdt.dsf.concurrent.Sequence$2.handleSuccess(Sequence.java:413)
at org.eclipse.cdt.dsf.concurrent.RequestMonitor.handleCompleted(RequestMonitor.java:353)
at org.eclipse.cdt.dsf.concurrent.RequestMonitor$2.run(RequestMonitor.java:298)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

regards

ahsan

[selom]

Hello Ashan, thanks for the reply and stacktrace.

Can you please provide me with the following information to help with my investigation?

1. Your operating system

2. Playbook NDK version

3. Version of java installed. Typing "java -version" in your command line window will show the version info.

4. The path value in workspace_loc

Cheers

Selom

[ahsan_iqbal]

Hi Selom

Here is some information

OS: win7 64bit.

NDK version:2.1

Java version: 1.6.0_26

workspace_loc:E:\work\Blackberry\Projects 

and thats exactly my workspace is 

Regards

Ahsan

[smacmartin]

This seems related to

http://supportforums.blackberry.com/t5/Native-Development/Problems-with-SDK-update/td-p/1596771

Did this one get resolved?

Did you just install the NDK as is?

workspace_loc is a path variable of eclipse: http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc.user%2Fconcepts%2Fconcepts-...

Please check your path settings in eclipse.  e.g. for GoodCitizen, project properties, resource, linked resource I have WORKSPACE_LOC set to C:\blackberry\ndk-2.0.0-workspace

Do you have a corresponding setting, and can you access that directory?

(I'm expecting based on the documentation that this is the same variable as the lower-case property used by eclipse.  I have not had to change these settings so can't be sure of the impact.)

Stuart

[ahsan_iqbal]

I somehow figured out issue, Issue was I had removed some library projects from my worksapce, and I also removed references of those projects from the main project, but IDE or launcher still trying to locate those projects from workspace, when copied and pasted those projects back in workspace issue got resolved.