| 3 Oct 2023 |
 sevenrats | but, this is not the correct solution, and I'm not even sure what the problem is | 04:26:46 |
 Izzie | I would try reproducing the commands in the build pipeline: https://github.com/jellyfin/jellyfin-media-player/blob/698e18e2eb105e3e42bd772ebf8f875b65fe51b7/.github/workflows/main.yml#L10-L39 | 04:26:48 |
|  Jason Raimondi joined the room. | 04:27:06 |
| Izzie | specifically that fix-install-names.py looks like it could help, if I remember right | 04:27:09 |
| Izzie | * specifically that fix-install-names.py looks like it could help, if I remember right | 04:27:24 |
 Dangles | In reply to @elegantbeef:matrix.org
Is there any documentation on Fields inside the getEpisodes procedure? Are you referring to the Fields that can be requested from the server when calling getEpisodes? | 04:27:55 |
|  n37w0rk joined the room. | 04:27:53 |
 Elegantbeef | Yea | 04:28:01 |
| Dangles | In reply to @elegantbeef:matrix.org
Yea I'm kinda new, but I think it's these ones:
https://github.com/jellyfin/jellyfin/blob/master/MediaBrowser.Model/Querying/ItemFields.cs | 04:28:45 |
| Elegantbeef | Thanks | 04:28:54 |
| sevenrats | In reply to @iwalton3:matrix.org
Looks like it is missing ffmpeg (libavcodec) oh you know what it is, is all these libraries are installed in the brew Cellar not where the script expects them | 04:29:40 |
| sevenrats | like, you are right about the script for sure but when I run it It finds libraries which are actually missing. like wtf is libiodbc.2.dylib | 04:30:19 |
| Izzie | In reply to @sevenrats:matrix.org
like, you are right about the script for sure but when I run it It finds libraries which are actually missing. like wtf is libiodbc.2.dylib it is a database connection library | 04:30:44 |
| sevenrats | i can install libiodbc with brew but of course it gets put in the Cellar is well. what do you think happened | 04:30:44 |
| Izzie | why it needs that is beyond me | 04:30:50 |
| Izzie | That's just where homebrew puts things. Did the fix names script help? | 04:31:15 |
| sevenrats | i mean it's presented a hell that I think a build might be on the other side of, but, im not even sure how to go back to zero at this point. | 04:31:48 |
| sevenrats | id like to just fix my build environment and produce a good build | 04:32:26 |
| sevenrats | In reply to @iwalton3:matrix.org
That's just where homebrew puts things. Did the fix names script help? ok fyi its not that deep of a hell. its just a couple libs that need to be installed with brew. then you run brew info thelib and it provides you with export statements that set cpp compiler flags | 04:40:46 |
| sevenrats | easy enough | 04:40:47 |
| Izzie | nice | 04:41:07 |
| sevenrats | hmm. doesn't fix it for the script of course tho. manual symlinks it is. | 04:41:44 |
| Izzie | hopefully the CI doesn't blow up the next time I run it | 04:42:05 |
| Izzie | although I would guess this is more because of M1 and QT 6 | 04:42:17 |
| Dangles | 
Download image.png | 04:43:14 |
| Dangles | Has anyone working on Jellyfin-web run into this webpack build issue?
| 04:43:17 |
| Dangles | Building on Windows btw, latest Node and NPM versions. | 04:43:42 |
 grhallenbeck | In reply to @dangles_:matrix.org
Has anyone working on Jellyfin-web run into this webpack build issue?
I've only been running it for a day or two so I haven't run into anything like this, but it could be a caching issue. You could try stopping webpack, then deleting node_modules/.cache, then restarting webpack. | 04:48:01 |
| Dangles | In reply to @grhallenbeck:matrix.org
I've only been running it for a day or two so I haven't run into anything like this, but it could be a caching issue. You could try stopping webpack, then deleting node_modules/.cache, then restarting webpack. Thanks, I'll give this a whirl | 04:50:12 |
| Dangles | Just in case anyone else sees this who has the same error.
I reckon I had some outdated path in my env vars from updating node. I delete node_modules and package-lock, then restarted my console and re-ran npm install | 05:29:40 |
