Replies: 11 comments
-
|
Can you try running Also as a side note: Is there a specific reason you want to build it yourself? If you just want to use it, there shouldn't be much reason to build it yourself. |
Beta Was this translation helpful? Give feedback.
-
|
Honestly, just assumed I needed to build it myself to use it properly. I knew that there's a web version, but I can't use hotkeys while tabbed in-game that way, so I figured I'd try building it myself just in case. Like I said before, I'm fairly new to Linux. Windows raised me ignorant to a lot of things, and resources on this particular issue were kind of hard to find haha. |
Beta Was this translation helpful? Give feedback.
-
|
@Kry0hh Can you try running that command in the |
Beta Was this translation helpful? Give feedback.
-
|
oh wait, is the submodule maybe just not checked out at all? Not sure if that's what the error would look like, but it's certainly a possible source of problems. |
Beta Was this translation helpful? Give feedback.
-
|
@wooferzfg I gave it a shot, sadly same error.. although, I will say that my livesplit-core folder is completely empty which doesn't seem right? I know 0 JS, so I could be wrong, but when I looked it up it it said cwd is to change the working directory. It's trying to to that to livesplit-core/capi/bind_gen, but there's no other files or folders inside livesplit-core right now. |
Beta Was this translation helpful? Give feedback.
-
|
@CryZe @wooferzfg Also sorry for my slow responses, but thanks for both your help. How would I check for that @CryZe ? |
Beta Was this translation helpful? Give feedback.
-
You do not have the submodules checked out. Try running the following then building again. I normally clone repos with |
Beta Was this translation helpful? Give feedback.
-
|
@DarkRTA I literally don't know HOW in the world I didn't clone the repo with recursive, since I'd done every command over a couple times while troubleshooting just to make sure... but yeah, that seems to have worked. I executed npm run build:core successfully! |
Beta Was this translation helpful? Give feedback.
-
|
it probably failed to figure out how to run your browser. the first few lines of output should contain the url the development server is listening on. just open that in your browser. But as @CryZe already said theres no difference than using the hosted version. it is exactly the same thing. The only advantage of hosting livesplitone yourself would be either you want to hack on it or maybe that when you write a websocket server to control it it would not have to be using secure websocket protocol.(#495 ) So in either way youd have to write a websocket server that livesplitone can connect to and that sends messages to control it when you press your hotkeys(Or search if someone already did this) there is a desktop version based on livesplit-core in the works but i dont think it is ready for general use yet. |
Beta Was this translation helpful? Give feedback.
-
|
out of curiousity hacked togheter a simple example https://github.com/mgolisch/lso-remote
|
Beta Was this translation helpful? Give feedback.
-
|
Yeah, it seems both Firefox and Chrome have exceptions for SSL when talking to localhost. #275 (comment) |
Beta Was this translation helpful? Give feedback.
-
Fairly recently I've made the switch over from windows. Usually I'm able to troubleshoot on my own with this sort of thing, but I've never had to build like this before. I have Rust Compiler and NPM all setup, but I'm having trouble when trying to run npm start. This is the output I get:
Up until this point, everything went alright. No errors or anything that weren't just stupid little mistakes on my end. Hoping this is just another stupid mistake haha
Sorry for such a newbie question. But any help would be greatly appreciated!
Also, if it helps. I'm on Manjaro, so I'm Arch-based, and here's the log file from the above screenshot:
log_file.log
Beta Was this translation helpful? Give feedback.
All reactions