!flDUDlxzYhNVyLEcSA:bonifacelabs.ca

Jellyfin Client Development

4733 Members
Development discussion of Jellyfin client projects. See the space for more rooms: #jellyfinorg:matrix.org77 Servers

Load older messages


SenderMessageTime
3 Oct 2023
@sevenrats:matrix.orgsevenratsbut, this is not the correct solution, and I'm not even sure what the problem is04:26:46
@iwalton3:matrix.orgIzzieI would try reproducing the commands in the build pipeline: https://github.com/jellyfin/jellyfin-media-player/blob/698e18e2eb105e3e42bd772ebf8f875b65fe51b7/.github/workflows/main.yml#L10-L3904:26:48
@jasonraimondi:matrix.orgJason Raimondi joined the room.04:27:06
@iwalton3:matrix.orgIzziespecifically that fix-install-names.py looks like it could help, if I remember right04:27:09
@iwalton3:matrix.orgIzzie * specifically that fix-install-names.py looks like it could help, if I remember right 04:27:24
@dangles_:matrix.orgDangles
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
@_discord_817496987372224562:t2bot.ion37w0rk joined the room.04:27:53
@elegantbeef:matrix.orgElegantbeefYea04:28:01
@dangles_:matrix.orgDangles
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:matrix.orgElegantbeefThanks04:28:54
@sevenrats:matrix.orgsevenrats
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:matrix.orgsevenratslike, 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.dylib04:30:19
@iwalton3:matrix.orgIzzie
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:matrix.orgsevenratsi can install libiodbc with brew but of course it gets put in the Cellar is well. what do you think happened04:30:44
@iwalton3:matrix.orgIzziewhy it needs that is beyond me04:30:50
@iwalton3:matrix.orgIzzieThat's just where homebrew puts things. Did the fix names script help?04:31:15
@sevenrats:matrix.orgsevenratsi 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:matrix.orgsevenratsid like to just fix my build environment and produce a good build04:32:26
@sevenrats:matrix.orgsevenrats
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:matrix.orgsevenratseasy enough04:40:47
@iwalton3:matrix.orgIzzienice04:41:07
@sevenrats:matrix.orgsevenratshmm. doesn't fix it for the script of course tho. manual symlinks it is.04:41:44
@iwalton3:matrix.orgIzziehopefully the CI doesn't blow up the next time I run it04:42:05
@iwalton3:matrix.orgIzziealthough I would guess this is more because of M1 and QT 604:42:17
@dangles_:matrix.orgDanglesimage.png
Download image.png
04:43:14
@dangles_:matrix.orgDanglesHas anyone working on Jellyfin-web run into this webpack build issue? 04:43:17
@dangles_:matrix.orgDanglesBuilding on Windows btw, latest Node and NPM versions.04:43:42
@grhallenbeck:matrix.orggrhallenbeck
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_:matrix.orgDangles
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_:matrix.orgDanglesJust 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 install05:29:40

There are no newer messages yet.


Back to Room ListRoom Version: 5