语言

Menu
Sites
Language
native-packaging and/or native-install are broken

Hi everyone,

After going through a cycle of frustration, unable to determine why our projects fail to run, I discovered that native-packaging and/or native-install appear to be broken in the current Tizen 2.2.1 SDK on Windows.

For example, I can native-gen and empty project, native-make within the "CommandLineBuild" directory, then native-packaging and native-install within that folder. The resulting executable never runs. native-debug reveals an error like this one:

Cannot access memory at address 0x0
[Inferior 1 (process 21582) exited with code 0377]

This is the same problem we were having with our own projects. I've always taken working binaries from a Tizen IDE project, and pasted it into a command-line packaged project, and the result is the same -- something about the IDE's packaging and/or install works, while running from the command-line does not, at least here on Windows. This is a big problem, because we cannot use the Tizen IDE -- we need to be able to build on a command-line.

Is there anyone who can help with this? We're new to Tizen, so I don't have a reference point to say how long this has been broken, etc. Does anyone else see the same problem? Could it be that our development device is running an old (bugged) build?

Thanks!

列表

响应

2 回复
Pushpa G

Refer to https://developer.tizen.org/forums/native-application-development/application-crashes-instantly

And also before installing new version:

1)Uninstall old version

2)Delete all its left out folders

3)Then install the new version of the sdk

4)Generate certicicate(ref: http://127.0.0.1:1468/help/topic/org.tizen.gettingstarted/html/dev_env/certificate_generator.htm), set active the generated certificate in Tizen SDK>Secure profile

Then build and run your apps

Joshua Granick

I got it to work after switching systems. I think that I accidentally missed that "native-make" targets i386 by default, instead of specifying the architecture myself. I did get the sample empty project to run, so I'm going to try and use that as a litmus test for determing what funny business prevents our application from executing.

How does Tizen know which executable to run? Is it "bin/$(name).exe", or is it from the --rpath when linking?

Thank you