Is it possible to have the (non-SDL.net) SDL libraires embedded inside the XBMC executable?, or alternatively have them included in the XBMC application folder and then either loaded and static libraries or DLLs?
My point is that I would like XBMC for Windows to not be dependent of third-party libraries downloaded from other sides than XBMC, and also for XBMC not to (indirectly) be dependent on the .NET framework (by using the SDL.net version of XBMC).
Would it not be better if we included the correct version needed for XBMC in the SVN and when compiled only have XBMC use them, so it is not shared with other applications the users run on their Windows-computer that requires SDL. That way the user would never have to update SDL separately from the XBMC binaries, and the user would always get the correct version of SDL when they update or reinstall XBMC for Windows.
Oh, and the same question goes for GLEW, could that also be pre-packaged with XBMC for Windows, and in our SVN?
User-friendliness and independence from other applications being the key. I think XBMC would be use user-friendly if with the exception of the unique UserData profile, everything that XBMC needs to run should be included in "C:\Program Files\XBMC\"; the XBMC executable, the correct version of the SDL library files, and the correct version of the GLEW library files.
My point is that I would like XBMC for Windows to not be dependent of third-party libraries downloaded from other sides than XBMC, and also for XBMC not to (indirectly) be dependent on the .NET framework (by using the SDL.net version of XBMC).
Would it not be better if we included the correct version needed for XBMC in the SVN and when compiled only have XBMC use them, so it is not shared with other applications the users run on their Windows-computer that requires SDL. That way the user would never have to update SDL separately from the XBMC binaries, and the user would always get the correct version of SDL when they update or reinstall XBMC for Windows.
Oh, and the same question goes for GLEW, could that also be pre-packaged with XBMC for Windows, and in our SVN?
User-friendliness and independence from other applications being the key. I think XBMC would be use user-friendly if with the exception of the unique UserData profile, everything that XBMC needs to run should be included in "C:\Program Files\XBMC\"; the XBMC executable, the correct version of the SDL library files, and the correct version of the GLEW library files.
