JamPlus

Well, I guess the silence either means people are happy with JamPlus (possible), people don't know about JamPlus (most likely), or they just don't want to talk about JamPlus. :)

The nextgen branch is where most development has occurred. Its most important update is multiple toolchain support. In one invocation of JamPlus, a whole variety of platforms and configurations can be built. This is especially important when dealing with PS3 builds where there is a PPU compiler and an SPU compiler. See below for an example.

Xcode 4.2 support has been added, but Xcode 4.3 support (which just came out) has not.

iOS 5 is also supported.

Primary development along the master branch has ceased, but I do bring in bug fixes. I do know that organizations are using the master branch and will provide bug fixes, if possible, when requested. I might backport features like iOS 5 support to the master branch, but in general, the nextgen multi-toolchain support is far more powerful.

Let me know if you have further questions.

Josh :)

################################
C.Toolchain vs2008 win32 debug x86 ;
C.Defines helloworld : MY_DEFINE ;
C.Application helloworld : main.c ;

###################################
C.Toolchain win32custom debug ;
C.Defines helloworld : MY_DEFINE ;
C.Application helloworld : main.c ;

###################################
C.Toolchain tcc debug ;
C.Defines helloworld : MY_DEFINE ;
C.Application helloworld : main.c ;

################################
C.Toolchain win32 debug x86 ;
C.Defines helloworld : MY_DEFINE ;
C.Application helloworld : main.c ;

################################
C.Toolchain vs2010 win32 release x86 ;
C.Defines helloworld : MY_DEFINE2 ;
C.Application helloworld : main.c ;

################################
C.Toolchain vs2010 win32 debug x86 ;
C.Defines helloworld : MY_DEFINE2 ;
C.Application helloworld : main.c ;

################################
C.Toolchain win32 release x86 ;
C.Defines helloworld : MY_DEFINE2 ;
C.Application helloworld : main.c ;

How is the dependency setup between the toolchains ?

Given the ps3 example you end up with a acouple of different object compiles then a single link, how does that relate to what you have above ? ( im guessing what you have above would generate 1 executable per tool chain)

(just in the middle of making the switch to try the new nextgen branch :) )

Steve.

So, in reality, there is no such thing as a toolchain. There are only targets.

Assuming something theoretical like:

C.Toolchain ps3 debug spu ;
C.Object abc.o : abc.c ;

C.Toolchain ps3 debug ppu ;
C.Library myps3lib : whatever.cpp <ps3!debug!spu>abc.o ;

So the dependency is based on the name of the fully gristed target <ps3!debug!spu>abc.o.