this post was submitted on 26 Apr 2024
831 points (97.6% liked)
Open Source
31223 readers
306 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You can put in a timeout command at the end, and then call the next .bat file.
For example "TIMEOUT /T 60" waits for 60 seconds before resuming, or you can override it by pressing any key.
So if you know how long the wait time between scripts is, just write a master.bat and call them in order, with adequate waiting time in between.
This guy is a master bat-er
Or just use the
@CALLcommand to call them in order without having to guesstimate how long they run.Okay so the dumb part is a lot of this is me abstracting away our complex build system. I've basically bubble-gummed a dedicated build system in top of it for only the tasks I do. At a certain point if I start adding configurations or timing I might as well just wrap it in gradle or something. But the system that I'm calling is already their attempt at simplifying another build system that's underneath it that was written by the old guard using arcane sorcery. The whole thing is a mess