So seeing that caveman had exactly the same problem I had, even the error message was the same (cwstudios told me caveman had the problem, but I didn't think the same problem)
My main question is this: how far is the code updated on github? According to what cwstudios told caveman to do here…
cwstudios wrote:It's in the repository under CAVEMAN-TENNY. Some things that you need to do to get this mac ready is.
1. change all occurences of StdCallCallback (StdCallbackLibrary) to Callback (Library) you can use ctrl-f to find all of them.
2. remove all reference to windows api’s. should be easy to find because they make your app crash when you launch
3. remove the dispatch message calls (peekMessage/dispatchMessage/translateMessage)
4. copy the edsdk framework to /Library/Frameworks or /System/Library/Frameworks
5. you’ll have to fiddle with the library loading a bit. it’s inside CanonCamera (i think)
6. if you would like to use callbacks (e.g. for downloading images) make sure to have some awt window open. calling
seems to be enough to get the nsapplication loop going.
7. before you run anything you need to add
To the JVM arguments to force 32bit mode. The canon edsdk isn’t 64bit mode yet for Mac it's developmental on windows according to them. Make sure you DO NOT push these changes to the windows version repo I can make a new one for mac or you can make it.
…he finally got it working on Windows 7 I think. Those steps required a lot of changing the code and there's a complete difference between the Windows code now and the Mac code. Did caveman update any of the stuff he did to the repo?
caveman wrote:Instead, I'll just make a new comment. It claims that the build was successful despite several lapses, and I am comletely unsure if these are significant or not.
So caveman, I want to say this. The build was successful because syntax and the general code is complete, and will run properly. However, there's a meathod that is called, and it threw this exception when trying to start the program.
This is a long shot, but if we catch the error like this it might at least open up the window and show the components.
try{//what the meathod that is causing this error is called
}catch(UnsatisfiedLinkException e){// Do nothing}
I do it all the time: catching an error and doing nothing it he try block fails.
If the meathod is totally important, no matter what camera you're using or where any files are, we needn't catch that meathod.
Last edited by jasper (March 30, 2013 (11:22pm))
