Enter the query into the form above.
API method:
GET /api/symbols?search=hello&page=1&limit=20
where search is your query, page is a page number and limit is a number of items on a single page. Pagination information (such as a number of pages and etc) is returned
in response headers.
If you'd like to join our channel webring send a patch to ~whereiseveryone/toys@lists.sr.ht adding your channel as an entry in channels.scm.
Return the DT_RUNPATH dynamic entry of FILE as a list of strings, or #f if FILE lacks dynamic info.
Return dynamic-link information for ELF as an <elf-dynamic-info> object, or #f if ELF lacks dynamic-link information.
Replace occurrences of '$ORIGIN' in STR with DIRECTORY.
Return two values: the list of absolute .so file names FILE depends on, recursively, and the list of .so file names that could not be found. File names are resolved by searching the RUNPATH of the file that NEEDs them.
This is similar to the info returned by the 'ldd' command.
Return the effective version of GUILE or whichever 'guile' is in $PATH. Return #false if it cannot be determined.
Return paths under `output' for scm and go files for effective version of GUILE or whichever `guile' is in $PATH. Raises an error if they cannot be determined.
Build the given Guile package, applying all of PHASES in order.
Build from SOURCE to OUTPUTS, using INPUTS, and by running all of PHASES in order. Return #t if all the PHASES succeeded, #f otherwise.
Build the given Haskell package, applying all of PHASES in order.
Fetch CHANGESET from URL into DIRECTORY. CHANGESET must be a valid Mercurial changeset identifier. Return #t on success, #f otherwise.
Generates the plugin.xml file that is required by Maven so it can recognize the package as a plugin, and find the entry points in the plugin.
Install jar files from JAR-DIRECTORY to the default target directory. This is used in case the build.xml does not include an install target.
Install a jar archive and its pom-file to a maven repository structure in lib/m2. This requires the parent pom file, if any, to be present in the inputs of the package being built. This phase looks either for a properly named jar file (artifactID-version.jar) or the single jar in the build directory. If there are more than one jar, and none is named appropriately, the phase fails.