Off-Topic > SCM EXtensions

SCM buildin how-to

<< < (3/6) > >>

vinnie:
ok, I tried to run buildscm for your script (sh buildscm ./circuslinux-sc.inc /apps/circuslin
ux), I did the wrapping operation, but circusilinux does not work:


--- Code: ---tc@box:/apps/circuslinux/bin$ ./circuslinux

Warning: I could not open the options file for read:
/home/tc/.circuslinux
The error that occured was:
No such file or directory


Error: I could not load the music file:
/apps/circuslinux/share/circuslinux/data/music/finally.mod
The Simple DirectMedia error that occured was:
Unrecognized music format

tc@box:/apps/circuslinux/bin$

--- End code ---

However, as a matter of mere teaching I tried a package even easier (with no dependencies) to create a working script, and this time I succeeded:
http://sprunge.us/KfCR?bash (sorry for italian comment)
Practically I'll have to do the same work for each dependency and then include it with ". . /dep-sc.inc" in master file,

what would the next steps?
1)wrapping (in this case  is usefull)
2)create icons and desktop file in /apps/packname/share/pixmaps and applications (automatically linked from scm-load when pack mounted)
3)purge /apps/packname from undesired file
4)put eventually start script (install) and variables/flag file (spec) in /apps/packname/config
5)make pack with mksquashfs ./packname packname.scm
it is all?


Two more question
1) it possible to create a database containing a list of all "-sc.inc" so that we can reuse them when needed to build new scm?
2) i see your tcz converting script, this makes me think that the settings given during the compilation does not make incompatible the two types of packets with each other.
it is possible in some way merge the two builds in one?

This remind me the old .tce (but I can not figure out if there are real similaritudes)

P.s. thanks Jason

Jason W:
It appears that a dependency of circuslinux was not successfully built, which should have resulted in the build stopping.  I will try downloading the files and building again.

Converting tcz's works for some apps, not for all, and some other things have to be done on a case by case basis.

Basically those steps you describe is how it works.

A database of -sc.inc files is possible, but some apps need a particular version of something and also perhaps built a certain way, so those cases would need to run their own particular build files.

vinnie:

--- Quote ---Converting tcz's works for some apps, not for all, and some other things have to be done on a case by case basis.

--- End quote ---
only asked to streamline in some way the creation of the two types of packets, basically i am lazy  :)


--- Quote ---A database of -sc.inc files is possible, but some apps need a particular version of something and also perhaps built a certain way, so those cases would need to run their own particular build files.

--- End quote ---
We could distinguish the different versions by name.
But effectively, now you make me think, your script is just a method for making the scm, but someone might like to use other.

If I can, I will try to make a package scm seriously this day.

vinnie:
It took me a while because I did not know which program to choose, I ended up with a program called gargoyles, interactive fiction interpreter.
After various adventures I managed to compile it, but now I'm a bit undecided how to proceed.

in addition to ftjam that I will have to create it myself (but just the TCZ, this is tool for compilation), I need this tcz to compile normally gargoyle:

tce-load -i compiletc SDL-dev SDL sdl-sound-dev sdl-sound libvorbis-dev libvorbis smpeg gtk2-dev

However things that should be included in /apps/packname are only the start dependencies, so how do I proceed?
Install all tcz build dep for gargoyle start dep and compile this in scm style?
And for gtk2 use export before compiling start dep.
These exports are used to tell the program where to find libraries after being compiled?


P.s. stealing the PKGBUILD from aur, startup dependencies "should" be these:
gtk2 sdl_mixer sdl_sound libvorbis freetype2

Jason W:
Gtk2 apps will need to be built against this tarball package:

http://distro.ibiblio.org/tinycorelinux/4.x/x86/scm/gtk2-dev.tar.xz

Just uninstall gtk2.scm and untar that xz in /apps.

Compiletc.tcz and perhaps it's related development tcz's should be your only tcz's you depend on.  SDL, gtk2, smpeg, they should be installed in the scm, or be depended on in the case of gtk2.scm.

There are -sc.inc files for sdl and libvorbis in the source area.

Navigation

[0] Message Index

[#] Next page

[*] Previous page