building a package from source is most of the time
1. unpacking the source archive
2. ./configure __with_some_options
4. make install DESTDIR=SOME_TEMPORARY_FOLDER_HOSTING_THE_BUILT_FILES
But of course there are a lot of exceptions.
What I usually do is
1. I use a metascript (slackgenerator) that writes a skeleton
2. I unpack the archive to a temporary folder
and look at the README, INSTALL, etc. to find out
about specific options
3. If there's a configure script, I run
and see if there are any specific options to add
to the SlackBuild script
4. I copy the apname.SlackBuild to source folder, edit
it to remove any unecessary stuff and test it step by step
by commenting out everything except the first step (e.g., configure)
If there are errors (such as a missing library, I try to install
them before proceeding)
Then I continue: make, etc.
Sometimes there are no configure script but an autogen.sh
or just a plain Makefile
Some files need to be tweaked once in a while (Makefile, etc.)
I do it with sed
I learned a lot by looking at the src2slack script
(sorry, I forgot who wrote it), the SlackBuild scripts
at the slackbuild web site, and of course from the SlackBuilds
found in the source directory of slackware.
I suggest you first try to build some simple stuff
starting from a SlackBuild found in the source tree of
the slackware distro.
Start with the ones that only have
make install DESTDIR=$PKG