LDECODE

NAME
SYNOPSYS
DESCRIPTION
NOTES
SEE ALSO
COPYRIGHT

NAME

ldecode - retrieve the original content encoded with lencode(1) within a open-lmake job

SYNOPSYS

ldecode association_file context code

DESCRIPTION

ldecode may be used to ask for a value (typically rather large) associated with a short code. This must have been generated using the command lencode(1) with the same association_file and context. The value corresponding to code is output on stdout.

It is an error if

association_file is not a source (symbolic links are followed, though)

code cannot be found with the accompanying context

Usage and use cases are more extensively documented the full open-lmake documentation.

NOTES

(1)

The same functionality is provided with the lmake.decode python function.

(2)

lencode(1) and ldecode are useful tools when the flow implies file names whose names are impractical. This is a way to transform long file names into much shorter ones by keeping an association file to retrieve long info from short codes.

(3)

Using this functionality may imply git(1) conflicts on the association file when several users independently create associations in their repos. This is fully dealt with and the only thing left to the user is to accept the resolution of the conflict without any action.

SEE ALSO

lautodep(1), lcheck_deps(1), ldebug(1), ldepend(1), lencode(1), lforget(1), lmake(1), lmark(1), lrepair(1), lrun_cc(1), lshow(1), ltarget(1), xxhsum(1)

The python module lmake.

The full open-lmake documentation in <open-lmake-installation-dir>/docs/index.html.

COPYRIGHT

Copyright © 2023-2025, Doliam. This file is part of open-lmake.

open-lmake is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, version 3 of the License.

open-lmake is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.