- Prefers to be called
- Uses pronoun
- Wroclaw, Poland
- 4 years 10 months ago
- Last seen
- 1 day 3 hours ago
Thanks, Jaymie for the answer. Unfortunately, even taking example of "vuoize" stateless node (which of course compiles ok when not edited) and changing extension to .cc and including iostream causes same error:
17:48:26: Running steps for project example.stateless... 17:48:26: Configuration unchanged, skipping qmake step. 17:48:26: Starting: "/usr/bin/make" /Users/dumski/Qt/5.9.5/clang_64/bin/qmake -o Makefile example.stateless.pro -spec macx-clang CONFIG+=debug CONFIG+=x86_64 CONFIG+=qml_debug ../../../framework/vuo-compile --output example.stateless.vuoize.vuonode example.stateless.vuoize.cc && mkdir -p ~/Library/Application\ Support/Vuo/Modules && cp example.stateless.vuoize.vuonode ~/Library/Application\ Support/Vuo/Modules example.stateless.vuoize.cc:11:10: fatal error: 'iostream' file not found #include <iostream> ^ 1 error generated. example.stateless.vuoize.cc: error: Broken node — The node <code>example.stateless.vuoize</code> couldn't be compiled to bitcode. Check the macOS Console for details. make: *** [example.stateless.vuoize.vuonode] Error 1 17:48:26: The process "/usr/bin/make" exited with code 2. Error while building/deploying project example.stateless (kit: Desktop Qt 5.9.5 clang 64bit) When executing step "Make" 17:48:26: Elapsed time: 00:01.
Also, passing path to Xcode's iostream with --header-search-path sometimes work, but a lot of other errors appear.
I googled whole day and cannot make it compile. I read that adding -stdlib=libstdc++ flag can tell compiler explicitly to use standard C++ library, but adding this option to vuo-compile causes "unrecognized option" error. I even don't understand what is the role of vuo-compile while developing a node? Is it some kind of "host" which redirects compilation to other compiler, or it's compiler itself? Because CMake outputs only command starting vuo-compile and I wondered if vuo-compile passes a compilation somwhere else, or does some "quiet" compilation using clang/clang++?
Can you explain the process of compiling a node?
Thank you, Teo
I wanted to make a new feature request for something like de-summarize node and end up here. I think it's a very useable feature since we have a bunch of TREE nodes. Now we can take various data from our compositon (like settings of calibration adjusted for a very long time) and save them as JSON file. But a lack of de-summarizing node (for points, color, numbers, text/numvers lists, etc.) forces us to decode back a tree using dozens of nodes.
For example, to put a 4 points into saveable JSON: take a look at "save-4points" image. And now, to put only first of this points into VuoPoint2d back: take a look at "read-4points" image. Imagine nodes for decoding some 4d matrices or color palette...
I think vuo-nodes-wide de-summarize function will lift whole Vuo system up and make data manipulation symmetric.