Mit dem Wii Construction Set lassen sich mit Hilfe einer GUI C-Projektfiles für Wii-Applikationen erstellen, die man dann mit einem Compiler zu DOL bzw. ELF-Files kompilieren kann. Es soll als eine Art Assistent dienen, ähnlich wie der Wii Game Maker. Nachfolgend die englische Beschreibung samt Installationsanleitung:
--------------------------------------------
Wii Construction Set Installation:
--------------------------------------------
WCS is a program for creating Wii platform C code. Using a simple GUI with Pseudo Code a user can create his/her desired project and then WCS will convert it into C code which can be compiled with readily available compiler toosl such as DevKitPro.
To use WCS you do not need DevKitPro or GRRLIB installed. However after WCS creates your project's c code you will need both DevKitPro and GRRLIB installed on your PC to create your executable file (which can then be run on the Wii).
1. Installing Wii Construction Set
The Wii Constructin Set Installation ZIP file expands to 2 ZIP files.
1.1 Studio
One file is the Studio ZIP file which contains all the necessary files to run the WCS GUI environment. This environment is used to create the actual project using a varierty of provided commands. With only this component installed you can create projects and save them but you can not actually have WCS generate the final c code.
The installation is designed to run from the expanded directory with no system files being copied to your computer (except those in the extracted directory). This means there is no Windows Uninstall entry created for this program but it also means that you can remove it simply by deleting the directory (with no residual files left on your system).
So to instal this portion of WCS, just extract the file to the desired directory. Although the program can be run from a USB device (or theoretically even a CD) it is recommended to run from hard drive since this will increase program performance. During testing I was running it from a USB key and it worked fine but was a little slow.
1.2 WiiConSet
The other file in the Installation ZIP archive is the WiiConSet file. This portion of WCS is used to make the actual c code when you ask WCS to compile your project for you. This portion of WCS can only be installed if DevKitPro has already been installed. The contents of this file must be extracted into the examples folder of your DevKitPro directory. For example, if you installed DevKitPro in C:\DevKitPro then you would need to extract this archive into C:\devkitPro\examples.
By extracting the archive into the example directory, it will create a subdirectory called WiiConSet. The directory will contain the Makefile (compile instructions) to compile your project with DevKitPro. The directory will also contain a batch file which can be run to start the compile process and one to copy the results your SD card (to apps/test).
Please remember that the compile process in WCS is to convert your project's pseudo code to c files, it does not actually compile your project to an Wii executable. However, as was mentioned above, a batch file is provided to start the compile process which is peformed by the DevKitPro compiler. Assuming everything is installed properly, by running the provided batch file after using the WCS Compile option, you should get a fully working Wii executable file (DOL and ELF).
If you are interested in studying the resulting c files (that WCS turned your project into) you can check out the source subdirectory. There should be 4 files present (main.c, Objects.c, Support.c and SupprtVar.c). The main.c file contains the high level instructions for the project. This file is common to all projects (i.e. will be the same for all projects). The Object.c file contains the structure used to store information about objects and the low level object functions. It is also common to all projects. Support.c holds all the project specific instructions including object drawing and all the user programmed events. Lastly SupportVars.c contains all the user defined variables. In addition the gfx sub-directory contains all the images and image c/h files for all the project images.
2. Installing DevKitPro
Download the DevKitPro installer. Run the installer. Unless you are worried about hard drive space, you can keep all options selected. I highly recommend installing the Programmer Notepad if you plan to do any c code editing (i.e. editing not done in WCS). It is a text editor but geared to programming.
This component is needed to compile your c code (produced by WCS) to an actual Wii executable.
Note: Since WCS does not use DevKitPro (it just makes c code that DevKitPro or another compiler can compile) it is not subject to any of the DevKitPro license agreements. However, any c code (produced by WCS or not) that is compiled with DevKitPro becomes subject to the DevKitPro license agreement. It is the user's responsibility to ensure that this license agreement is upheld if the resulting project will be distributed.
3. Installing GRRLIB
GRRLIB is one of many graphics libraries abailable on the Wii platform. Although WCS does not use GRRLIB itself, the c code that it crates uses GRRLIB to perform its graphical functions. Thus you will need GRRLIB installed if you plan to compile your (WCS provided) c code to a Wii executable file.
The following steps indicate how to install GRRLIB:
1. Download the GRRLIB Trunk Installation
2. Change to the GRR\Trunk\GRRLIB\Lib directory
3. Execute the sub-library install by typing: install
4. Change to the GRR\Trunk\GRRLIB\GRRLIB directory
5. Execute the library install by typing: make clean all install
This installation process can also be found in the GRRLIB Trunk download.
If you have problems, please see the posts on the WCS Forum regarding installation (if any). If this does not resolve your problem, make a new post with details regarding your problem.
--------------------------------------------
Wii Construction Set Installation:
--------------------------------------------
WCS is a program for creating Wii platform C code. Using a simple GUI with Pseudo Code a user can create his/her desired project and then WCS will convert it into C code which can be compiled with readily available compiler toosl such as DevKitPro.
To use WCS you do not need DevKitPro or GRRLIB installed. However after WCS creates your project's c code you will need both DevKitPro and GRRLIB installed on your PC to create your executable file (which can then be run on the Wii).
1. Installing Wii Construction Set
The Wii Constructin Set Installation ZIP file expands to 2 ZIP files.
1.1 Studio
One file is the Studio ZIP file which contains all the necessary files to run the WCS GUI environment. This environment is used to create the actual project using a varierty of provided commands. With only this component installed you can create projects and save them but you can not actually have WCS generate the final c code.
The installation is designed to run from the expanded directory with no system files being copied to your computer (except those in the extracted directory). This means there is no Windows Uninstall entry created for this program but it also means that you can remove it simply by deleting the directory (with no residual files left on your system).
So to instal this portion of WCS, just extract the file to the desired directory. Although the program can be run from a USB device (or theoretically even a CD) it is recommended to run from hard drive since this will increase program performance. During testing I was running it from a USB key and it worked fine but was a little slow.
1.2 WiiConSet
The other file in the Installation ZIP archive is the WiiConSet file. This portion of WCS is used to make the actual c code when you ask WCS to compile your project for you. This portion of WCS can only be installed if DevKitPro has already been installed. The contents of this file must be extracted into the examples folder of your DevKitPro directory. For example, if you installed DevKitPro in C:\DevKitPro then you would need to extract this archive into C:\devkitPro\examples.
By extracting the archive into the example directory, it will create a subdirectory called WiiConSet. The directory will contain the Makefile (compile instructions) to compile your project with DevKitPro. The directory will also contain a batch file which can be run to start the compile process and one to copy the results your SD card (to apps/test).
Please remember that the compile process in WCS is to convert your project's pseudo code to c files, it does not actually compile your project to an Wii executable. However, as was mentioned above, a batch file is provided to start the compile process which is peformed by the DevKitPro compiler. Assuming everything is installed properly, by running the provided batch file after using the WCS Compile option, you should get a fully working Wii executable file (DOL and ELF).
If you are interested in studying the resulting c files (that WCS turned your project into) you can check out the source subdirectory. There should be 4 files present (main.c, Objects.c, Support.c and SupprtVar.c). The main.c file contains the high level instructions for the project. This file is common to all projects (i.e. will be the same for all projects). The Object.c file contains the structure used to store information about objects and the low level object functions. It is also common to all projects. Support.c holds all the project specific instructions including object drawing and all the user programmed events. Lastly SupportVars.c contains all the user defined variables. In addition the gfx sub-directory contains all the images and image c/h files for all the project images.
2. Installing DevKitPro
Download the DevKitPro installer. Run the installer. Unless you are worried about hard drive space, you can keep all options selected. I highly recommend installing the Programmer Notepad if you plan to do any c code editing (i.e. editing not done in WCS). It is a text editor but geared to programming.
This component is needed to compile your c code (produced by WCS) to an actual Wii executable.
Note: Since WCS does not use DevKitPro (it just makes c code that DevKitPro or another compiler can compile) it is not subject to any of the DevKitPro license agreements. However, any c code (produced by WCS or not) that is compiled with DevKitPro becomes subject to the DevKitPro license agreement. It is the user's responsibility to ensure that this license agreement is upheld if the resulting project will be distributed.
3. Installing GRRLIB
GRRLIB is one of many graphics libraries abailable on the Wii platform. Although WCS does not use GRRLIB itself, the c code that it crates uses GRRLIB to perform its graphical functions. Thus you will need GRRLIB installed if you plan to compile your (WCS provided) c code to a Wii executable file.
The following steps indicate how to install GRRLIB:
1. Download the GRRLIB Trunk Installation
2. Change to the GRR\Trunk\GRRLIB\Lib directory
3. Execute the sub-library install by typing: install
4. Change to the GRR\Trunk\GRRLIB\GRRLIB directory
5. Execute the library install by typing: make clean all install
This installation process can also be found in the GRRLIB Trunk download.
If you have problems, please see the posts on the WCS Forum regarding installation (if any). If this does not resolve your problem, make a new post with details regarding your problem.