Spanish Version


+ Introduction

+ About Us

+ Downloads

+ Source Code

+ Dev. Environment

+ SODIUM Developer Kit

+ Configuration

+ Testing & Installation


+ Try SODIUM Online




EjecuciĆ³n e InstalaciĆ³n

Testing and Installing SODIUM

In order to compile, test, or install SODIUM it is necessary to have completed its configuration first. Once the configuration is generated, it is possible to run any of the following commands shown below.

In order for these commands function, they have to be executed from the SODIUM's root folder.

Running Tests

In order to run a test as was configured using configurar.sh, it only takes to execute the following command:

    # make test

Once ran, SODIUM will compile, and the bootable device images will be generated. If the results of the compilation is successful, an instance of Bochs will be created and will start booting SODIUM:

If the code was already compiled from a previous instance, running "make test" only will not include any new changed in the code. In case of having made changes, you should first eliminate all compiled images and code and recompile them again. In order to do that in a single step, you can run:

    # make clean test

 

Installing SODIUM

In order to install a bootable instance of SODIUM in a physical device (with the configuration set using configurar.sh) you must run the following command:

  # make install

In case of having made changes to the code, you may run this command instead:

    # make clean install

 

Other Useful Commands

In order to clean all binaries, intermediate compilation files, and bootable images, you may run:

# make clean

This command eliminates all compilation-generated files (excluding Makefile.cfg) and leaves all SODIUM folders in their original state after the SVN checkout. This specially useful to evaluate which changes were made to the code without the interference of generated files.

In order to generate automated documentation of the code using Doxygen, you may run:

# make docs