i tried to give the addon the same structure as i saw i vaMice. The
tweener already uses a namespace ie. tween
thats what i wrote in the CMakeListes.txt file
SET( TWEEN_ROOT ${PROJECT_SOURCE_DIR}/addons/tween )
#set includes, also make available in parent scope
SET( TWEEN_INCLUDES
${TWEEN_ROOT}/include
)
SET( TWEEN_INCLUDES
${TWEEN_ROOT}/include
PARENT_SCOPE
)
INCLUDE_DIRECTORIES( ${TWEEN_INCLUDES} )
ADD_LIBRARY( tween STATIC
${TWEEN_ROOT}/include/tween/CppTweener.h
${TWEEN_ROOT}/src/CppTweener.cpp
)
TARGET_LINK_LIBRARIES( tween
va ${VA_LINK_LIBRARIES}
tween
)
SET_TARGET_PROPERTIES( tween PROPERTIES
ARCHIVE_OUTPUT_DIRECTORY ${TWEEN_ROOT}/bin
)
And the folder structure in the addon is as follows:
addons
– tween
– – include
– – – tween
– – – – CppTweener.h
– – src
– – – CppTweener.cpp
– – CMakeListes.txt
I also changed the "#include "CppTweener.h" to "#include <tween/
CppTweener.h> in CppTweener.cpp
Then i thought, it should be possible to include the tweener via
#include <tween/CppTweener.h> in my MyApp.h, but xcode told me, that
it couldnt find the file/directory.
What is wrong?
Thanks for any answers.
Matthias
Maybe a tuio connection to community core vision, for example. How
hard would it be, to get this up and running? Will it be worth to put
some effort into this? Or are you working on things like that anyway?
Thanks for listening
Matthias
The way you have set up the tween addon looks correct. How about the
master CMakeListes.txt file? At the end there is a section where all
the addon directories are added. Have you added the tween addon
directory there? Something like ADD_SUBDIRECTORY( addons/tween )
should do the trick so cmake is aware of the new directory.
Let me know how it goes,
/stefan
OPTION( BUILD_ADDON_TWEEN "Build the CPP Tweener addon." ON)
IF( BUILD_ADDON_TWEEN )
ADD_SUBDIRECTORY( addons/tween )
ENDIF()
but still the include through #include <tween/CppTweener.h> doesnt
work. What am i missing?
right, osg has an animation plugin. It's quite extensive. Just be
aware that the current va release only comes with a small selection of
osg plugins (for simplicity). It is relatively easy to compile a
complete osg yourself or just let me know and I can send you binaries.
> Maybe a tuio connection to community core vision
tuio is based on UDP networking and OSC. Networking addon is in the
works ;) but I haven't thought about osc yet. If you want to give it a
shot let me know. I'll get the networking addon ready.
There is also a vaTouchkit addon in the release. It's a minimal ccv
with super clean blob tracking code. Currently it is specific to the
firefly cams though.
/stefan
For reference, I just uploaded a branch with the tween addon working.
It's in the git repo:
http://github.com/stefanix/VirtualAwesome/tree/cpptweener
There are no support libs in the repo so you will either have to pick
the files you want and copy them to your release copy. Or you will
have to copy all the support libs to the git checkout. Either way
should work.
Let me know if you have questions,
/stefan
Still playing around with va and osg, slowly getting an understanding
how everything is related.
I would like to try something with shadows, found a nice example in
the osg download package. I am able to compile this under xcode with
the help of the osg osx installation i found here
http://www.cuboslocos.com/tutorials/OSG-GettingStarted
Now, when i try to add pretty much the same code to a va project,
during linking xcode says:
Undefined symbols:
"osgShadow::ShadowedScene::setShadowTechnique(osgShadow::ShadowTechnique*)",
referenced from:
MyApp::MyApp() in MyApp.o
MyApp::MyApp() in MyApp.o
"osgShadow::ShadowedScene::ShadowedScene(osgShadow::ShadowTechnique*)",
referenced from:
MyApp::MyApp() in MyApp.o
MyApp::MyApp() in MyApp.o
"osgShadow::ShadowMap::ShadowMap()", referenced from:
MyApp::MyApp() in MyApp.o
MyApp::MyApp() in MyApp.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
I guess thats because osgShadow is not really part of the VA-project
somehow?
Actually this is mostly an example question for how to access the full
power of osg within va. Maybe this is of interest for others too?
Eventhough it seems i'm the only loudmouth on this list so far?
Do i need another osg-compilation? And where do i put it?
However, thanks for your work!
Matthias
good to hear
> I would like to try something with shadows
> Undefined symbols
> I guess thats because osgShadow is not really part of the VA-project
> somehow?
that is correct. In va-0.4.2 we only included a small selection of osg
plugins. For the next release there is a good chance we include a
complete osg. We'll see. What you can do for now is download a
complete osg and drop it in the va libs directory instead of
'osg-osx'. Here is the download:
http://virtualawesome.googlecode.com/files/osg-2.8.2-osx-10.5-static-release-all.zip
Let us see some shadows if you get it working!
> i'm the only loudmouth on this list so far?
Yes va is still very new ... kudos to the early adopters ... ;)