자바 cv에서 IplImage 생성이 안됩니다.
public void onCreate(Bundle savedInstanceState)
{
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_LANDSCAPE);
mButton = (Button) findViewById(R.id.button);
mPhotoImageView = (ImageView) findViewById(R.id.image);
cvCard = IplImage.create(10,10,IPL_DEPTH_8U,1);
mButton.setOnClickListener(this);
}
위의 소스코드에서 cvCard = IplImage.create(10,10,IPL_DEPTH_8U,1);
실행하면 프로그램이 바로 죽어버립니다. 컴파일은 문제 없이 되구요.
컴파일 되는거 자체가 javacv path 같은것은 제대로 잡아준것이라고 생각하는데 혹시 아닌가요?
이유를 몰라서 path를 잘못잡아줘서 그런가 생각도 해봤는데 path가 제대로 안 잡혔으면 컴파일도 안될꺼라고 생각했는데..
첨부파일에 로그도 함께 올렸습니다.
공지사항 읽었습니다.
해결 방안 찾다가 예제있는곳 찾아서 똑같이 만들어서 해봤는데
똑같이 했는데도 이상한 에러가 발생하네요.
위와 같이 셋팅하고 소스에 아무런 오류가 안났는데 실행시키니깐
[2012-05-20 16:55:10 - javacv] Dx
trouble processing "java/cv/BuildConfig.class":
Ill-advised or mistaken usage of a core class (java.* or javax.*)
when not building a core library.
This is often due to inadvertently including a core library file
in your application's project, when using an IDE (such as
Eclipse). If you are sure you're not intentionally defining a
core class, then this is the most likely explanation of what's
going on.
However, you might actually be trying to define a class in a core
namespace, the source of which you may have taken, for example,
from a non-Android virtual machine project. This will most
assuredly not work. At a minimum, it jeopardizes the
compatibility of your app with future versions of the platform.
It is also often of questionable legality.
If you really intend to build a core library -- which is only
appropriate as part of creating a full virtual machine
distribution, as opposed to compiling an application -- then use
the "--core-library" option to suppress this error message.
If you go ahead and use "--core-library" but are in fact
building an application, then be forewarned that your application
will still fail to build or run, at some point. Please be
prepared for angry customers who find, for example, that your
application ceases to function once they upgrade their operating
system. You will be to blame for this problem.
If you are legitimately using some code that happens to be in a
core package, then the easiest safe alternative you have is to
repackage that code. That is, move the classes in question into
your own package namespace. This means that they will never be in
conflict with core system classes. JarJar is a tool that may help
you in this endeavor. If you find that you cannot do this, then
that is an indication that the path you are on will ultimately
lead to pain, suffering, grief, and lamentation.
[2012-05-20 16:55:10 - javacv] Dx 1 error; aborting
[2012-05-20 16:55:10 - javacv] Conversion to Dalvik format failed with error 1
opencv 가 저런 것도 있었나요?
전 직접 ndk 로 빌드했었는데 ;;