Start Terminal.app in Applications folder.<\/li>\n<\/ol>\nTips: By dropping a file or folder from Finder into Terminal.app’s window, you will get full path of the file\/folder appearing at the end of command line. if you type ‘cd\u00a0<\/code>‘ before drop, you can get something like ‘cd \/Users\/you\/foo<\/code>‘.<\/p>\n\n- Do
cd<\/code> to the root directory, SCCToolKit.<\/li>\n- Do
mkdir build ; cd build<\/code>.<\/li>\n- Run
ccmake ..<\/code>. If you want Xcode to do debug, do ccmake -GXcode ..<\/code><\/li>\n- Type ‘c’ once. ccmake will ask you where’s your OpenCV, Qt and DeckLink SDK.<\/li>\n
- After ccmake successfully identifies these, you type a few more ‘c’ and you can finish ccmake by typing ‘g’.<\/li>\n
- Run
make<\/code>. This will build the library and sample programs in Examples.<\/li>\n- If everything goes fine, you get
make<\/code> complete with 100% done<\/code>.<\/li>\n- Play with the examples.<\/li>\n<\/ol>\n
Step 3: Build Apps in SCCToolKit<\/h2>\n
To build application programs in Apps directory, you need to do similar to the above process. For example,<\/p>\n
\n- Do
cd<\/code> to Apps\/lkdemo<\/code>.<\/li>\n- Do
mkdir build ; cd build<\/code><\/li>\n- Run
ccmake ..<\/code><\/li>\n- Type
c<\/code> once. This case, you need to tell ccmake where is SCCToolKitConfig.cmake<\/code> file, which is in ..\/..\/build<\/code> in above example.<\/li>\n- After finding
SCCToolKitConfig.cmake<\/code> and do some customization, type ‘c’ a few more and if you are satisfied to your setting, type ‘g’.<\/li>\n- Run
make<\/code>. When successful, you will get an executable file (App) in build\/bin\/<\/code><\/li>\n- Play with App.<\/li>\n<\/ol>\n
Enjoy happy hacking!<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"NOTE: This project is \u2018dormant\u2019 and no longer updated. This page is posted for referencepurpose. Contents here may not be valid under current environment. Step 0: Prepare Necessary Resources Currently, SCCToolKit runs only on OS X 10.7 to 10.10. This is due to the use of CoreImage and libdispatch library and Apple’s language extension of […]<\/p>\n","protected":false},"author":11,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_locale":"en_US","_original_post":"http:\/\/scc.pj.aist.go.jp\/?p=1131","footnotes":""},"categories":[21],"tags":[],"_links":{"self":[{"href":"http:\/\/127.0.0.1\/wp-json\/wp\/v2\/posts\/3755"}],"collection":[{"href":"http:\/\/127.0.0.1\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/127.0.0.1\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/127.0.0.1\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"http:\/\/127.0.0.1\/wp-json\/wp\/v2\/comments?post=3755"}],"version-history":[{"count":3,"href":"http:\/\/127.0.0.1\/wp-json\/wp\/v2\/posts\/3755\/revisions"}],"predecessor-version":[{"id":4467,"href":"http:\/\/127.0.0.1\/wp-json\/wp\/v2\/posts\/3755\/revisions\/4467"}],"wp:attachment":[{"href":"http:\/\/127.0.0.1\/wp-json\/wp\/v2\/media?parent=3755"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/127.0.0.1\/wp-json\/wp\/v2\/categories?post=3755"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/127.0.0.1\/wp-json\/wp\/v2\/tags?post=3755"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}