+- 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: Could use help verifying setup to compile SDL XBMC. (/showthread.php?tid=31915)
Could use help verifying setup to compile SDL XBMC. - djdafreund - 2008-03-13
Hey, i would really appreciate some help in order to start building the SDL/OpenGL version of XBMC. So far, i followed the Wiki for SDL instructions using VC++ 2003, the proper xbmc_lib paths added to include and lib, and as well as the proper linuxbuild SVN location. I want to make sure these messages are either normal, or if it's going to create problems.
http://pastebin.com/f2287127d
Also, Right now i'm using the build\batch build method within VC++ 2003, and checked the last one in the list "XBMC_PC Release(SDL) Win32 Release(SDL) Win32", and choose Build/or Rebuild. Since the Build.bat file doesn't seem to work with the SVN for SDL builds. At least it's giving me an error message when i tried, that's why i am having to use the 'XBMC_PC.vcproj' file to build it. Is there an easier method for building? I couldn't find any actual build instructions in the Wiki other then settings up and then "Now you should be able to build the project".
Right now i am using the regular Xbox/XBMC dx version Build.bat to be able to make my xbox and xbmcdx builds to get the correct updated remaining XBMC directory files, and because i co-design Back-Row skin.
Thanks for any help you can give me. I'm really trying here, and just want some help, and verification if i'm doing things correct, and if any easier methods to build other then having to use the 'XBMC_PC.vcproj' file, which only leave's by default the XBMC.exe file only.
Thanks BIG time for any responses guys. It will be much appreciated.
- jmarshall - 2008-03-13
Looks fine - as long as there's no error's. Warnings are OK.
- WiSo - 2008-03-13
How could it be easier than pressing build in visual studio?
- djdafreund - 2008-03-13
I Appreciate the sarcasm WiSo, not everyone was born with a VB spoon in there mouth. The thing is, I have '0' experience with using Visual Studio, i did mention i am already doing that currently, but maybe you just missed reading that part. But since i saw those messages after trying 1st, and don't practice just doing things without knowledge of what i'm doing when i DO start having unknown issues, it's safer to ask 1st. And the one time i built it, it froze each it time i clicked on any video links and crashed XBMC, the 2nd time seems to work fine. That's why i wanted to ask if those messages were meaning anything important, that's all. Thanks JMarshall for that info. I appreciate that.
- WiSo - 2008-03-14
Come one dude this was a fair question and only regarding the
Quote:...and if any easier methods to build other then having to use the 'XBMC_PC.vcproj' file...Since jmarshall already answered I just don't wanna repeat it.
- djdafreund - 2008-03-14
Well, i appreciate JMarshall's answer anyway. But what i meant about an easier method to build is(maybe i just wasn't clear enough the way i asked.), i meant instead of like how "Build.bat" actually downloads/or updates the SVN, compiles, and rar's up a file with the .exe file, the xbmc updated directories and such with the DX version, currently you have to load up VB++, compile which only gives you the .exe file, run Build.bat and compile that to get the XBMC directories themself's, and then grab the 'glew32.dll' file and include that in the zip as well.
That's more of what i meant by an easier method. Maybe i should've asked instead a question like, "Is there any way to modify the 'Build.bat' file to work with the XBMC SDL version?" I guess that was my fault for not being more specific to my meaning of easier method to build EVERYTHING of xbmc sdl version in one pass like you can with the DX version. So that's cool about your question. So is it possible to modify the Build.bat file to work with building the SDL version?
- jmarshall - 2008-03-14
I just:
1. Load the solution.
2. Make sure it's set on whatever output you want (release/debug).
3. Hit F5.
I don't bother with "building a release" or anything - it should straight out of the SVN folder. Ofcourse, I haven't actually tested that for a while, and you probably don't want to have visual studio open all the time :p
There's probably not too much wrong with build.bat - possibly just where it outputs the files that is incorrect (and ofcourse removing all the xbox stuff).
Cheers,
Jonathan
- djdafreund - 2008-03-14
This is pasted from when trying to run Build.bat
------------------------------------------------------------
XBMC prepare menu
------------------------------------------------------------
[1] Build XBMC XBE ( for XBOX use )
[2] Build XBMC_WIN32 ( for Windows use)
------------------------------------------------------------
Please enter the number you want to build! [1/2]:2
Wait while preparing the build.
------------------------------------------------------------
Cleaning Solution...
Microsoft ® Development Environment Version 7.10.3077.
Copyright © Microsoft Corp 1984-2001. All rights reserved.
Invalid solution configuration
Usage:
devenv [solutionfile | projectfile | anyfile.ext] [switches]
You can invoke devenv with a first argument to specify a solution file or
project file. You can also invoke devenv with a first argument that is any
other kind of file that you just want to open in an editor. When you supply a
project file, the IDE opens it in the context of a solution by looking for a
.sln file with the same base name as the project file in the same
directory as the project file. If no such .sln file exists, then the IDE
looks for a single .sln file that references the project. If no such single
.sln file exists, then the IDE creates an unsaved solution with a default .sln
file name that has the same base name as the project file.
Command line builds:
devenv solutionfile.sln /build solutionconfig [ /project projectnameorfile [ /p
rojectconfig name ] ]
Available command line switches:
/build build the specified solution configuration
/project specifies the project to build instead of solution
must specify /build to use /project
/projectconfig specifies project configuration to build
must specify /project to use /projectconfig
/out write build output to specified file
/rebuild like /build but forces a clean first
/clean clean up build outputs
/deploy build the specified solution configuration and then deploy it
/run run the specified solution configuration
/runexit run the specified solution configuration and then terminate
/command executes the specified internal command line after startup
/mditabs use tabbed documents interface
/mdi use MDI interface
/fn use specified font name
/fs use specified font size
/LCID use specified language ID
/noVSIP disables VSIP developers license key for VSIP testing
/safemode only default environment and services load for stability
/resetskippkgs allow VsPackages once flagged for loading failures to
load again
/migratesettings migrate some user settings from another version
Product-specific switches:
/debugexe Open the specified executable to be debugged. The
remainder of the command line is passed to this
executable as its arguments.
/useenv Use PATH, INCLUDE, LIBPATH, and LIB environment variables
instead of IDE paths for VC++ builds.
To attach the debugger from the command line, use:
vs7jit.exe -p <pid>
The system cannot find the file specified.
Compiling Solution...
Microsoft ® Development Environment Version 7.10.3077.
Copyright © Microsoft Corp 1984-2001. All rights reserved.
Invalid solution configuration
Usage:
devenv [solutionfile | projectfile | anyfile.ext] [switches]
You can invoke devenv with a first argument to specify a solution file or
project file. You can also invoke devenv with a first argument that is any
other kind of file that you just want to open in an editor. When you supply a
project file, the IDE opens it in the context of a solution by looking for a
.sln file with the same base name as the project file in the same
directory as the project file. If no such .sln file exists, then the IDE
looks for a single .sln file that references the project. If no such single
.sln file exists, then the IDE creates an unsaved solution with a default .sln
file name that has the same base name as the project file.
Command line builds:
devenv solutionfile.sln /build solutionconfig [ /project projectnameorfile [ /p
rojectconfig name ] ]
Available command line switches:
/build build the specified solution configuration
/project specifies the project to build instead of solution
must specify /build to use /project
/projectconfig specifies project configuration to build
must specify /project to use /projectconfig
/out write build output to specified file
/rebuild like /build but forces a clean first
/clean clean up build outputs
/deploy build the specified solution configuration and then deploy it
/run run the specified solution configuration
/runexit run the specified solution configuration and then terminate
/command executes the specified internal command line after startup
/mditabs use tabbed documents interface
/mdi use MDI interface
/fn use specified font name
/fs use specified font size
/LCID use specified language ID
/noVSIP disables VSIP developers license key for VSIP testing
/safemode only default environment and services load for stability
/resetskippkgs allow VsPackages once flagged for loading failures to
load again
/migratesettings migrate some user settings from another version
Product-specific switches:
/debugexe Open the specified executable to be debugged. The
remainder of the command line is passed to this
executable as its arguments.
/useenv Use PATH, INCLUDE, LIBPATH, and LIB environment variables
instead of IDE paths for VC++ builds.
To attach the debugger from the command line, use:
vs7jit.exe -p <pid>
------------------------------------------------------------
!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-
ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR ERROR
!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-!-
ERROR: XBMC_PC.EXE failed to build! See .\tools\Win32\Release\BuildLog.htm for
details.
------------------------------------------------------------
- C-Quel - 2008-03-14
pastebin
- djdafreund - 2008-03-14
Right, sorry. Was in a rush to leave my house.
- jmarshall - 2008-03-14
First thing is it can't find the solution file.
- djdafreund - 2008-03-14
I guess i'll try to figure out what a solution file is then and go from there. I am thinking maybe to modify a new Build.bat file out of this, and maybe hopefully get it included in the SVN tree (in the proper area of course), maybe named something like "Build.SDL.bat" or something like that. Others would love that i'm sure.
- CrazyIvan - 2008-03-14
djdafreund Wrote:I guess i'll try to figure out what a solution file is then and go from there.
http://xbmc.svn.sourceforge.net/viewvc/xbmc/branches/linuxport/XBMC/xbmc.sln?view=log
- WiSo - 2008-03-14
This one is for the SDL build:
http://xbmc.svn.sourceforge.net/viewvc/xbmc/branches/linuxport/XBMC/tools/Win32/XBMC_PC.sln?view=log
- djdafreund - 2008-03-14
Thanks WiSo, and thanks for the work your putting into it. It's very much appreciated. Enjoy the weekend!!