-
Notifications
You must be signed in to change notification settings - Fork 77
Build instructions #95
Comments
I'm joining in under this issue, some clarification on the build instructions would be useful. I'm confused on how to build Calla too. I did the following
I then opened the solution in Vistual Studio and tried to build but got this
And now I'm not sure how to fix this. I have a |
Hi folks, Apologies. I've been playing fast and loose with my repos lately for my project at work (a VR project which uses Calla under the hood). I'll be removing the Juniper, SignalR, and ASP.NET dependencies soon. The resonance-audio dependency is a git submodule because I had to fork Resonance (and its dependency, Omnitone) to fix several egregious defects that Google left in them when they basically abandoned the projects two, three years ago. |
I've set up a Calla installation using one of the first commits in this repo, before the asp.net changes. This is what I added to the jitsi docker-compose:
Of course this is not the latest version and does not have all the features as the current one, but I didn't want to have to mess around with asp.net :) |
archiving |
Is it possible to build and run this locally without ASP.NET? If so, how?
In the meantime, I'm trying to just
npm run build
-- is there a reason why resonance-audio is handled by a git submodule, while soundr is handled by libman? Instead of both being handled the same way, e.g. by npm dependencies?The text was updated successfully, but these errors were encountered: