I forked BJSn a week ago. I did the git
commands, but got a not found on cmake. I have VS community 2017, and thought it was in there & must have a path problem. It was Friday, and I just dropped it there.
Another Friday has arrived. I see that this fork was already 24 comits behind, which is good. I see the plugins got some attention. Reading the directions a little more closely this time, I went and got cmake
& an up to date Python
. (Exokit / node-gyp build requires an old Python
).
I did a pull from the original repo to get the changes for the week, and did a cmake ..
. A bunch of stuff scrolled by, including a bunch of Missing
message. Almost never a good sign. I did not redirect the output so I don’t have it, but just kept on going to see what happened next.
After starting VS, I did not have the option to change to win64. Only a win32 build, but I hit F5 anyway. Got a all these things are out of date. I continued on. A whole page of stuff listed out with a linker msg at the end saying no NativeEngine.lib
.
My VS was a year out of date, so I updated it (my OS, win10/64 was also updated this week). F5 again and only 2 things out of date. Still gets the same linker error, but now with only a couple of lines, this one jumped right out.
C:\BabylonNative\Plugins\NativeEngine\Source\NativeEngine.cpp(4): fatal error C1083: Cannot open include file: 'arcana/threading/task_schedulers.h': No such file or directory
I made a complete mess, & can easily just blow this away, and start over. Just thought I would relay this, first.
Question, should I even be forking this? I think I want to make a WebAudio
plugin as a wrapper around GitHub - LabSound/LabSound: graph-based audio engine . You have plugins, but they are all right in the same repo. Is this how I have to do it? Are you ready for this type of discussion yet? I have tons of other stuff to do, so that would not be a problem, if it was.