Making Modules

[Guy]

Can someone list all of the modules which need to be installed on Tiny Core for all aspects of making modules, and explain which part of the process each module is needed for?

[curaga]

Do you mean extensions?

TCE extensions can be created entirely with utils in the base (tar and md5sum). Advdef in advcomp.tce is optional, to reduce the size of a tce extension.

TCZ extensions need the tools to create the desired type (cramfs, zisofs, or in tc 2.x, squashfs).
The extensions are respectively cramfs-utils.tce, mkisofs-tools.tce and squashfs-tools-4.0.tce.

[Guy]

Thanks

I have been continually learning about making extensions.

Some things have not worked because I have not had the necessary modules installed.


What about other parts of the process.

For example, I recently tried to run ./configure and something was missing.

What modules need to be installed for other parts of the process?

[Juanito]

For example, I recently tried to run ./configure and something was missing.

What modules need to be installed for other parts of the process?

What error did you get with ./configure - if you're using tc_1.x, you need the compiletc extension loaded and if you're using tc_2.x, you need the gcc-binutils and base-devs extensions loaded.

[Guy]

Thanks

I have been continually learning different parts of the process, and the modules needed.

In the entire process from start to finish, are there any other modules which need to be installed?

[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

[Guy]

Thanks

I am continuing to learn