search

elliotwoods / VVVV.Packs.Image

VVVV addonpack for plugins dealing with CVImageLink
36 stars 31 forks source link

Documentation #22

Open elliotwoods opened 10 years ago

elliotwoods commented 10 years ago

Readme should be central point for all documentation and should discuss or point to further notes on:

elliotwoods commented 10 years ago

notes from @sebllll at #13 :

from @joreg :

and putting the \bin\x86 and \bin\x64 from this download into src\nodes\plugins\Image\OpenCV\Dependencies\OpenCV

as mentioned here: https://github.com/sebllll/VVVV.Packs.Image/tree/master/src/nodes/plugins/Image/OpenCV/Dependencies/OpenCV/x86

sebllll commented 10 years ago

i think the link in VVVV.Packs.Image\src\nodes\plugins\Image\OpenCV\Dependencies\OpenCV\x86\readme.md refers to a newer version than you used. is there any reason, why you don't use the latest emgucv/opencv-dlls?

elliotwoods commented 10 years ago

can you confirm which copy of the dll's you are referring to? i.e. you mean the ones in the Contributions download are older than on the emgu website?

elliot

sebllll commented 10 years ago

i had the old ones you are (249) using lying around here. but the link in the readme refers to the latest opencv-dlls which are 290.

sebllll commented 10 years ago

now, after you changed the place, where the pack should be placed for development, there are always missing references e.g vvvv.core, vvvv.utils and system.componentmodel.composition. i thought, they must be found automatically, if the imagepack is placed in the pack-folder...

just to make this clear, this is how my folders look like: image

and this is how the projects' references look like: image

of course, i can fix the references by myself and from hand, but i'm sure, you had a different idea. has it something to do with that 'new' nuget thing? can you document the usage of nuget a bit?

elliotwoods commented 10 years ago

First can you try the following:

Close VS and reopen Check the build configuration (all is x86 for example, no any CPU, no mix) Then... It should work Sometimes the interface complains about the references, but build works.

Let me know. @azeno will be documenting this

Typed by touchscreen

On 28 Nov 2013, at 14:12, sebl notifications@github.com wrote:

now, after you changed the place, where the pack should be placed for development, there are always missing references e.g vvvv.core, vvvv.utils and system.componentmodel.composition. i thought, they must be found automatically, if the imagepack is placed in the pack-folder...

just to make this clear, this is how my folders look like:

and this is how the projects' references look like:

of course, i can fix the references by myself and from hand, but i'm sure, you had a different idea. has it something to do with that 'new' nuget thing? can you document the usage of nuget a bit?

— Reply to this email directly or view it on GitHub.

sebllll commented 10 years ago

hmkay, it worked after hitting build (despite of missing references). does it try (and succeed) to fetch the references during build??

anyway, thanks for the progress!

azeno commented 10 years ago

well nuget should (in theory) download all missing dependencies when doing a build. but it sometimes doesn't work as advertised. not sure why. in any case, you can always right click the solution and select "Manage NuGet packages for solution...". there you'll see which packages are missing, installed or if there're any updates available. if you see those warning signs on the references, try reloading the solution after new packages have been installed, or make sure your build configuration (Debug/Release/x86/x64) is set properly. the VVVV.* nuget packages for example are only available for x86/x64. so setting the build configuration to AnyCPU will certainly bring up a warning sign on those references.

Hapboy commented 10 years ago

I have the same problem as sebl