[ironic_monkey]

yes, indeed it doesn't appear to be covering the folder over network case, only iso.

i was referring to these commits btw: https://github.com/xbmc/libdvdread/commits/master top three commits there which i think you will agree fits my description.

[Max_nl]

yes, indeed it doesn't appear to be covering the folder over network case, only iso.

i was referring to these commits btw: https://github.com/xbmc/libdvdread/commits/master top three commits there which i think you will agree fits my description.

Can see your point.


Still do not think that getting more complete and global vfs hooks added to libdvd is an impossible goal though.
And an option to indicate opendir/readdir is not possible would also make sense, given that could also happen to other media players in other situations (http).
If symlink resolving used the standard realpath() call, it would also be less of a problem to override / provide dummy function.

But then again, I do not know what upstream's stance is. Has the subject ever been discussed in the past?

[ironic_monkey]

you saw that reaction on the ticket? i rather such peeps stay out of my hair, and i of theirs. no such discussion have taken part afaik.

[Max_nl]

What would your own reaction be if another project would send an end-user to create three separate bug reports telling you to take unspecified commits with no proper commit log by anonymous author under unknown license out of a random repository, apply them and roll a new release?
And BTW if you have any questions, you should join the other's project forum, because that is the place where that is being discussed, and we have mailing list phobia...

Does that sums it up correctly?

[ironic_monkey]

sure, i do understand this particular reaction. i would probably react the same, but try to do it without all the spew
that's not a random end user btw, it's the guy doing gentoo packaging for kodi, so his goals were the same as yours.

just one example: if you know the history behind this; https://github.com/xbmc/libdvdnav/blob/m...nav.h#L389 you would understand why i, as a c++ dev, shy away. no, that was not an accident originally. it may very well be different these days but once bitten, twice shy.

[Memphiz]

https://github.com/MrMC/mrmc/commit/16a1...41d2bdac38

Might be related

[ironic_monkey]

yeh, i already have done the same but it doesn't cut it, we don't just support dvd isos.

[Max_nl]

nvm

[SgtPooki]

I'm trying to build kodi on Windows 10 right now and running into some trouble.

I'm not sure if this is the best place for this or not, but a link in the http://kodi.wiki/view/HOW-TO_compile_XBM...ource_code wiki is broken. Under the section http://kodi.wiki/view/HOW-TO_compile_XBM...or_Windows, a link for building the visual studio solution files using cmake points to https://github.com/xbmc/xbmc/blob/master...lding-kodi, but that only gets me to a 404.

I was able to find a working link by backtracking some comments and finding an old commit: https://github.com/xbmc/xbmc/blob/a4aaba...lding-kodi

Are those old instructions invalid? If so, what's the process for updating the wiki?

[fetzerch]

Thanks, we've moved the cmake project to the root directory which broke a few links. I've fixed the wiki page now, instructions are here: https://github.com/xbmc/xbmc/blob/master...lding-kodi