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*.scescript, if found, executes it; - otherwise, looks for a
builderscript in each subdirectory ofsrc/and executes them; - for
c, cpp, java, fortransubdirectories, if nobuilderscript is found, a default compilation process is done:ccompilation is done for all *.cfiles, headers must be present in thec/directory, function names must have the name of the file (without the.cextension)cppcompilation is done for all *.cpp or *.cxxfiles, headers must be present in thecppdirectory, function names must have the name of the file (without the.cpp or .cxxextension)javacompilation is done for all *.javafiles underorg/scilab/contrib/package_namedirectories wherepackage_nameis given by the userfortrancompilation is done for all *.ffiles
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
| Version | Description |
| 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 >> |
