From b7da1ad2f9e20b04b603b439ae570193398b5970 Mon Sep 17 00:00:00 2001 From: Daniel Schwyn Date: Mon, 24 Jul 2017 11:13:01 +0200 Subject: [PATCH] Sockeye: TN remove limitations chapter, update hake chapter Signed-off-by: Daniel Schwyn --- doc/025-sockeye/Sockeye.tex | 13 +++---------- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git a/doc/025-sockeye/Sockeye.tex b/doc/025-sockeye/Sockeye.tex index 75bce15772..bdb3acaa24 100644 --- a/doc/025-sockeye/Sockeye.tex +++ b/doc/025-sockeye/Sockeye.tex @@ -351,21 +351,14 @@ \chapter{Prolog Mapping for Sockeye} \lstinputlisting[caption={Generated Prolog code},label={lst:prolog_example},language=Prolog]{example.pl} -%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% -\chapter{Limitations} -\label{chap:limitations} -%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% -\section{Modularity} -\label{sec:modularity} -\todo{Add description of challenges} - %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \chapter{Compiling Sockeye files with Hake} \label{chap:hake} %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% -SoC descriptions are placed in the directory \pathname{SOURCE/socs} with the file extension \pathname{.soc}. -Each Sockeye file has to be added to the list of SoCs in the Hakefile in the same directory. +SoC descriptions are placed in the directory \pathname{SOURCE/socs} with the file extension \pathname{soc}. +Each top-level Sockeye file has to be added to the list of SoCs in the Hakefile in the same directory. The Hake rule for Sockeye files compiles all the listed files to \pathname{BUILD/sockeyefacts/.pl} if they are specified as a dependency in some Hakefile. +The rule will also generate a \pathname{.depend} file so that make recompiles the file also when imported files are changed. To add a compiled Sockeye specification to the SKB RAM-disk, the filename can be added to the \varname{sockeyeFiles} list in the SKBs Hakefile.