![]() ![]() The rest are the three C++ projects 2-4, that build the dynamic libraries (in the jar at META-INF/lib). So this would generate the missing class folder org.sikuli. This is the launch file, that is generated behind the respective Eclipse GUI (Project Properties -> Builders -> new) To mange this, I have made a general project containing only vision.i and setup an external Builder to fire the above SWIG command. usr/local/ Cellar/ opencv is the location, where I have the prereq stuff, since I use homebrew for package management sikuli/ sikuli- script/ src/main/ native/ vision. sikuli/ sikuli- script/ build/src/ main/native/ visionJAVA_ wrap.cxx I./sikuli/ sikuli- script/ src/main/ native I/usr/ local/Cellar/ opencv/ 2.2/include ![]() I/usr/ local/Cellar/ opencv/ 2.2/include/ opencv sikuli/ sikuli- script/ build/org/ sikuli/ script/ natives (separated on different lines to be more readable) The Java part is contained in VisionProxy.java, which is generated using the SWIG utility with the following call in the original cmake build: To call these functions from Java code, you have to implement a JNI (Java Native Interface). ![]() The functions, that use the OpenCV and Tesseract features are written in C++. The same way I use the build directory in the fork as the place for the compiled/generated stuff. I did it with an ANT workflow (see comment #1).Īnd remember: I do not copy any original source file from my sikuli fork to the Eclipse projects - everything is referenced as linked resources. Then copy all your newly compiled classes to the jar folder at to replace them and rebuild the jar file. Just unjar a running sikuli-script.jar, make a library reference to org.sikuli. step down to the native level and be able to deal with the native code too stay on the Java level (this is what you have now)Ģ. Now you must decide about your further steps based on what you want to achieve:ġ. 5 VisionSWIG (run swig via Eclipse externalToolBuilder)īased on my comment #1 and the mentioned steps and projects you need, it is the result of project 5 (I named it VisionSWIG), that is missing now. ** Step 1: made a fork from sikuli github repository () on my local machine (I am using the GitHub client for Mac) I have managed to set up an environment to build sikuli-script.jar from the sikuli/sikuli-script/src folder in Eclipse Indigo on Mac Lion. To clean, I currently delete the sikuli-script.jar manually, so it gets built again.īuild sikuli-script.jar Mac (Eclipse build) Since I told this project to be dependent on project 1 (sikuli-script), I just have to run this build.xml to get my running sikuli-script.jar. I decided to make a separate project with a build.xml, that puts together all needed stuff and finally creates sikuli-script.jar in the target directory of the local git fork. To clean, I currently delete the sikuli-script.jar manually, so it gets built again. So when I build sikuli-script (compile to create the class files), all the dependent stuff is built automatically, if something has changed. This was partly a little bit tricky with the g++ and linker options, but finally worked. and setting up the build environments for each project in Eclipse ** Step 3: analyze the Cmake/make files from the normal build 6 VDictProxy (still using the result from the package)Īll projects are setup with linked resources to the local github folder, so my changes are directly commitable to my fork on github. 5 VisionSWIG (run swig via Eclipse externalToolBui lder) ** Step 2: in Eclipse made different projects for the native and java stuff: com/RaiMan/ sikuli) on my local machine (I am using the GitHub client for Mac) ** Step 1: made a fork from sikuli github repository ( https:/ /github. I have managed to set up an environment to build sikuli-script.jar from the sikuli/ sikuli- script/ src folder in Eclipse Indigo on Mac Lion. should be rather easy, since it is a plain Java project and needs only library references to sikuli-script.jar and junit. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |