xbox 360 jam bugs

Added by Kevin Thacker over 5 years ago

this is used a lot in the xbo360-vc.jam (nextgen branch):

TARGET = [ _retrieveActiveTargetName $(TARGET) ] ;

e.g.

rule C.DeployXex TARGET : DEPLOY_LOCATION {
TARGET = [ _retrieveActiveTargetName $(TARGET) ] ;
DEPLOY_LOCATION on $(TARGET) = $(DEPLOY_LOCATION) ;
}

Should this just be:

C.ActiveTarget $(TARGET) ;

instead??

I have corrected it here.


Replies (5)

RE: xbox 360 jam bugs - Added by Kevin Thacker over 5 years ago

More:

In C.Application, should:

C._ApplicationTargetInfo ;

be changed to:

if [ RuleExists C.$(C.COMPILER_SUITE)._ApplicationTargetInfo ] {
C.$(C.COMPILER_SUITE)._ApplicationTargetInfo ;
}

so it can be set per platform?
so each toolchain can override it?

Then the rule in xbox360 can be:

rule C.vc._ApplicationTargetInfo {
}

The other rules in xbox360-vc.jam should have the ".vc." in them too?

RE: xbox 360 jam bugs - Added by Kevin Thacker over 5 years ago

in addition is this more correct:

DEBUGGEROUTPUTNAME on $(C.ACTIVE_TOOLCHAIN_TARGET) = $(_t:S=.xex:R=$(outputPath):G=) ;

rather than

DEBUGGEROUTPUTNAME.$(PLATFORM).$(CONFIG) on $(TARGET) = $(_t:S=.xex:R=$(outputPath):G=) ;

RE: xbox 360 jam bugs - Added by Kevin Thacker over 5 years ago

DEBUGGEROUTPUTNAME is not setup for vs2010 for example.

in vs201x.lua I added this:

if project.DebuggerOutputNames  and  project.DebuggerOutputNames[platformName]  and  project.DebuggerOutputNames[platformName][configName] then
configInfo.Output = project.DebuggerOutputNames[platformName][configName]
end

after this:

if project.OutputPaths and project.OutputPaths[platformName] and project.OutputPaths[platformName][configName]
and project.OutputNames and project.OutputNames[platformName] and project.OutputNames[platformName][configName] then
configInfo.Output = project.OutputPaths[platformName][configName] .. project.OutputNames[platformName][configName]
end

around line 124. And this fixed it in addition to using the

DEBUGGEROUTPUTNAME on $(C.ACTIVE_TOOLCHAIN_TARGET) = $(_t:S=.xex:R=$(outputPath):G=) ;

fix above.

I see that _ApplicationTargetInfo rule is ok as it is and doesn't need the .vc. in the name.

RE: xbox 360 jam bugs - Added by Joshua Jensen over 5 years ago

All bug reports in this thread have now been fixed in the nextgen branch.

I am leery about certain implementation details.

I don't think, for instance, that the xbox360 toolchain and regular vs20xx toolchain can be used within the same build without some additional refactoring.

I am pretty sure that the purpose behind C.Xbox360DeployToolSettings won't work under VS201x. If there is a public .vcxproj with these settings (maybe within Bullet?), then I can get that part going again.

-Josh

RE: xbox 360 jam bugs - Added by Kevin Thacker over 5 years ago

Joshua Jensen wrote:

All bug reports in this thread have now been fixed in the nextgen branch.

I am leery about certain implementation details.

I don't think, for instance, that the xbox360 toolchain and regular vs20xx toolchain can be used within the same build without some additional refactoring.

I am pretty sure that the purpose behind C.Xbox360DeployToolSettings won't work under VS201x. If there is a public .vcxproj with these settings (maybe within Bullet?), then I can get that part going again.

-Josh

It seems that Xb360 and Windows debuggers don't need any special information in the project file setting.
So both should be ok together.

Our Xb360 jam builds are working great now. Thanks for the help :)

Kev

(1-5/5)