tbx_builder_src
Builds the user source code (non-gateway) in src/
subdirectory.
Syntax
tbx_builder_src(toolbox_path)
Arguments
- toolbox_path
Root directory of toolbox sources; builder scripts will be searched in the src subdirectory of this directory.
Description
tbx_builder_src
is used for compiling the non-gateway code of a toolbox.
The compilation of sources in src/
directory follows this convention and priority order:
- looks for a
toolbox_path
/src/builder*.sce
script, if found, executes it; - otherwise, looks for a
builder
script in each subdirectory ofsrc/
and executes them; - for
c, cpp, java, fortran
subdirectories, if nobuilder
script is found, a default compilation process is done:c
compilation is done for all *.c
files, headers must be present in thec/
directory, function names must have the name of the file (without the.c
extension)cpp
compilation is done for all *.cpp or *.cxx
files, headers must be present in thecpp
directory, function names must have the name of the file (without the.cpp or .cxx
extension)java
compilation is done for all *.java
files underorg/scilab/contrib/package_name
directories wherepackage_name
is given by the userfortran
compilation is done for all *.f
files
The function exits silently if the src
directory is absent.
Little automation is done for tbx_builder_src and is only specified for c, cpp, java, fortran because source compiling is a very specific process. Toolbox developers willing to have a more specific compilation process still need to define what the build scripts must perform for compilation. |
Examples
// Recommended usage tbx_builder_src(get_absolute_file_path('builder.sce'))
History
Versão | Descrição |
6.0.0 | No longer restricts the build scripts to Automatically scans for builder scripts in subdirectories if no builder script is found in A default compilation process is introduced for |
Report an issue | ||
<< tbx_builder_macros | Sections builders | Helper functions >> |