+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Windows (https://forum.kodi.tv/forumdisplay.php?fid=59)
+---- Thread: [WINDOWS] Unofficial third-party nightly builds for the community (Notification only) (/showthread.php?tid=35452)
- kricker - 2009-10-08
Upped XBMC-Rev23535-GL
Upped XBMCSetup-Rev23535-GL
Upped XBMC-Rev23535-DX
Upped XBMCSetup-Rev23535-DX
- joshuass - 2009-10-09
23535 plays flawlessly DX and GL
Except.. someone put MSVCR90 and MSVCP90 dlls in the zipped builds.
Those cause R6034 error popups.
So hopefully, if anyone complains in the forums that's why.
EDIT: Removing the dll's causes no playback problems so that's what I'd recommend to users.
- azido - 2009-10-09
joshuass Wrote:23535 plays flawlessly DX and GL
Except.. someone put MSVCR90 and MSVCP90 dlls in the zipped builds.
Those cause R6034 error popups.
So hopefully, if anyone complains in the forums that's why.
EDIT: Removing the dll's causes no playback problems so that's what I'd recommend to users.
people capable of reading a few pages back already know about their issues & why they are applied.
- kricker - 2009-10-09
joshuass Wrote:Except.. someone put MSVCR90 and MSVCP90 dlls in the zipped builds.That someone was told to supply those. And despite the posts, I kept them in their as I have not officially been told otherwise yet. It is a work in progress. AKA SVN.
- joshuass - 2009-10-09
Oh! No worries.
And of course, since it is an SVN version, I do realize it is a work in progress, and there are bound to be issues, such as this.
Didn't mean to place blame and what not. My post was meant to be purely informational, despite how in hindsight, I could have reworded it better :o
My B
- jmarshall - 2009-10-09
What "R6034" popups are these? Unless we know the problem, we can't fix it.
Cheers,
Jonathan
- kricker - 2009-10-09
He's referring to this post:
http://forum.xbmc.org/showpost.php?p=415599&postcount=1019. Referring to that post, I don't get any such error with those .dlls in my xbmc folder.
Here are the .dlls I am using.
http://www.mediafire.com/file/yoz0wjywqiz/msvcr-p90.zip
- jmarshall - 2009-10-09
Thanks kricker.
It looks like we have two options:
1. Requiring that the installer includes the vc_redist.exe package.
2. Do a private assembly as per: http://msdn.microsoft.com/en-us/library/ms235291.aspx
The latter seems the ideal, depending on what exactly is asking for the dll (eg if it's a dll, does it use the path to the exe - I guess one can test it out?). Given that it's probably dll's as well as XBMC needing this stuff, number 1 may actually prove the less hassle long term?
Cheers,
Jonathan
- patkhoo - 2009-10-09
jmarshall Wrote:Thanks kricker.
It looks like we have two options:
1. Requiring that the installer includes the vc_redist.exe package.
2. Do a private assembly as per: http://msdn.microsoft.com/en-us/library/ms235291.aspx
The latter seems the ideal, depending on what exactly is asking for the dll (eg if it's a dll, does it use the path to the exe - I guess one can test it out?). Given that it's probably dll's as well as XBMC needing this stuff, number 1 may actually prove the less hassle long term?
Cheers,
Jonathan
Hi Jonathan, being a SW developer myself and our company is in the midst of looking into VS2008 migration as well, I must say I can identify with the problem you are talking about...
So far, our current thinking is that many (other) apps also need VC_redist, and that it may or may not have already been installed by users. So it is reasonable to have VC_redist as an optional install add-on. It would reduce our main program installer size..
On the other hand, it does mean changes in installer (no more portable) and more complicated for users who decide to download the installer (do I need to download VC_redist as well?) as opposed to it being shipped on a CD.
I don't know either, still thinking about it.. But you can be sure I will take close note of how you guys do it in the end..
- jmarshall - 2009-10-09
Yeah, I suspect the easiest thing to do is simply offer a link to the redist first and foremost (perhaps even from within the installer - it'd be nice if it was detectable) and get the user to install that first.
Cheers,
Jonathan
- kricker - 2009-10-09
I don't know the technical details behind it, but as a user, I prefer an app to be self contained without having to install other things. I like that I can just take the XBMC folder, zip it, and move it to another PC without having to to much of anything else. It has let me spread the software far and wide among friends without much hassle. This had been especially nice when the "net" has gone down and I didn't have an XBMC installer on hand to share (before I started creating my own builds and archiving them).
- jmarshall - 2009-10-09
Agreed. It's definitely worth trying stuff out with the private assemblies thing and seeing if that works - from the suggestions on MSDN, however, it looks like you need it per dll, and we scatter dll's all over the show (thus multiple copies may be needed).
- kricker - 2009-10-09
Upped XBMC-Rev23548-GL
Upped XBMCSetup-Rev23548-GL
Upped XBMC-Rev23548-DX
Upped XBMCSetup-Rev23548-DX
- HexusOdy - 2009-10-09
Hi Guys.
I'm using 23535-dx, my first attemp at using one of the DX builds. I tested it on my server rig today and all way great so I just put it on my Nettop that I use for streaming and decoding and I'm getting tearing.
The Nettop has Intel VGA, and there's a tonne of threads on the boards about tearing in Intel. CapNBry made a patch a long while back that fixed it in the GL version but it seems to be there again in DX.
Edit
Tried the GL version of same revision and there isn't any tearing. I'm guessing CapNbry's patch to fix the tearing was GL specific and a revision of it is needed for DX. But what do I know
- WiSo - 2009-10-10
Sorry for my late post but hadn't any time to look at the dll problem.
@jmarshall: the need for msvcp90.dll comes from the libass library. Just call a video with ass subtitles and you see the popup. The weird thing is that even if you don't have the dlls and get the 126 error message in the log libass still works fine.
Another option which requires a little more space is to compile libass (and future dlls) with static mfc. But dunno if this is a suitable solution.
@kricker: until you don't try out option 1 or 2 you can remove the dlls as it still works and nobody will complain.