XBMC4Xbox

To all of you out there that might have any input on this, I wouild love some pointers. I couldn't find concise instructions on this anywhere so I'll start here. I'm making my first build, and I don't know if I'm doing something wrong or if it's supposed to take FOREVER to make. So here's what I did:

- Opened up the solution in visual studio
- Made my changes (saved them)
- pressed build in visual studio (took a long time), and when it was done there was no build made...just a debug folder
- opened up the trunk and started the build process with the build bash file (taking equally as long I think, but still going)

what I am wondering about is:

- do I need to build in visual studio?
- do I close the solution when I'm done with my changes and then use the bash?
- do I point to a certain location for the BUILD folder to be placed?
- are there any settings inside of visual studio that need to be ticked or unticked?

That's pretty much all I've got for now, but any help would be appreciated (especially any pointers that would help speed up the learning curve).

- do I need to build in visual studio?
- do I close the solution when I'm done with my changes and then use the bash?
- do I point to a certain location for the BUILD folder to be placed?
- are there any settings inside of visual studio that need to be ticked or unticked?

1. depends - you chose to do a debug build - if you want to test small changes, using vs directly is the right way - the XBE will end up in Release or Debug depending
2. if you want - the batch files build the xbe and then package everything up in a BUILD/ folder (including skins etc)
3. no
4. only choosing which type of build you want.

http://www.xbmc4xbox.org.uk/wiki/HOW-TO ... ource_code is now available also but ignore the svn url etc as its out of date.

cool, thanks for the link. How do I make it package everything into one build (havn't checked the link yet)? And is it usual for it to take a very, very long time?

okay, so if you run the .bat it packages it for you..

byron wrote:cool, thanks for the link. How do I make it package everything into one build (havn't checked the link yet)? And is it usual for it to take a very, very long time?

well it's a lot of code and currently it is de-optimised in terms of precompiled headers being temporarily disabled so I could resolve inter-file/include dependencies problems. But still, it will take a while. Of course once built, you can change a file and rebuild/link without recompiling the entire tree.