I'm trying to build a custom module following the #2 method shown in the tutorial linked below.
http://www.porteus.org/tutorials/9-modu ... udies.html
The missing link for me is how to get dependencies that are already installed in PKDE into the module. When running slacky -d it only shows dependencies that are missing for packages already installed on the system. Do I need to download each of the below dependencies individually and move them to the ~/temp/modwork folder and reinstall them there so that they are part of the new module?
I guess I'm still unclear on how the modules are created. Is it required to have all of the .txz packages for each dependency in the fakeroot folder to build the custom module?
chardho
alsa-lib>1.0.24
fftw
libsamplerate
ncurses
pciutils
psmisc
docbook-xsl (make)
systemd (make)
xmlto (make)
Custom module dependency handling
Forum rules
Porteus Kiosk section of the forum is unmaintained now. Its kept in a 'read only' mode for archival purposes.
Please use the kiosk contact page for directing your queries: https://porteus-kiosk.org/contact.html
Porteus Kiosk section of the forum is unmaintained now. Its kept in a 'read only' mode for archival purposes.
Please use the kiosk contact page for directing your queries: https://porteus-kiosk.org/contact.html