Tiny Core Extensions > TCE Q&A Forum

Making Modules

<< < (2/3) > >>

MikeLockmoore:
From start to finish, it depends on what you are trying to build.  ;) But in many cases, the primary development extensions listed previously in this thread are enough.

The configure script for a particular package may use some specific tools (e.g. a python or perl interpreter) not in base or the primary development extensions.  So you might need to load these additional tools first.  The output of the ./configure command should help you figure out what other prerequisites you need.

Also, if you are trying to build a package from source code, that code may need to refer to information in header files that are not part of the base system ("X11 headers", for example), so you might need to load extensions with the appropriate set of source code headers. 
--
Mike L.

Guy:
Thanks for the info

When I have time, I will try to make extensions and see what happens. I will continue learning.


Another question with reference to

TCZ extensions need the tools to create the desired type (cramfs, zisofs, or in tc 2.x, squashfs).

In tc 2.x are three different types used, or are the previous ones being phased out?

curaga:
All three are supported, and there are no plans to drop support for any type. It's very low-maintenance to keep them around.

For 2.x the recommended format is squashfs, because it produces smaller extensions of the three. For 1.x it depends on the extension if cramfs or zisofs makes a smaller extension.

Guy:
What are the commands to make a module with squashfs?

curaga:
mksquashfs sourcedir extension.tcz

where sourcedir is the temporary root, the directory structure would be like this for aria2:
sourcedir/usr/local/bin/aria2c

Navigation

[0] Message Index

[#] Next page

[*] Previous page