A Interactive TCE Builder

[red]

I am developing a script that allows interactively creating TCE extensions. All you need to do is enter information for the extension (used for variables and .tcz.info), the HTTP link where the source is located (currently supported filetypes are .GZ, .TAR.GZ, .BZ2, .TAR.BZ2, and .TAR), it will detect the archive type, and build the package. If there is ./autoconf.sh in the source, it will execute that too. It is optional to use custom ./configure and make flags. The script also prepares a list of files and the md5sum of the .tcz extension.

I wll post a link to the .tcz when it will be ready. For now here are some screenshots:

[Juanito]

'looks interesting 

Most source packages are *tar.xz these days - it would be good to have support for that.

[red]

'looks interesting 

Most source packages are *tar.xz these days - it would be good to have support for that.

Added support for tar.xz!

[red]

Download link for tcz-studio 1.0-beta:
        http://www.mediafire.com/file/6213maykw3n3yqx/tcz-studio.rar

[Juanito]

I gave it a go on corepure64

It works with sed-4.2.2 

A couple of comments:

* bash is required as a dep
* the linux api headers are a dep of compiletc, so can be removed from the dep file
* the resulting /usr/local/bin/sed has permissions of tc:staff, but should have root:root
* /usr/local/bin/sed is not stripped
* the doc, info, man and locale files are not placed in *-doc and *-locale extensions

[jls]

hi
another build system is called tc-ext-tools hosted on github.

[red]

hi
another build system is called tc-ext-tools hosted on github.

Oh, well then.

[red]

I gave it a go on corepure64

It works with sed-4.2.2 

A couple of comments:

* bash is required as a dep
* the linux api headers are a dep of compiletc, so can be removed from the dep file
* the resulting /usr/local/bin/sed has permissions of tc:staff, but should have root:root
* /usr/local/bin/sed is not stripped
* the doc, info, man and locale files are not placed in *-doc and *-locale extensions

Okay, i got it. I also realized, that in some occasions the makefile might be located in another folder, or it has a different name, so i will add an option that if there are similar files beginning with Makefile*, it will ask which file should be used

Or if there is no makefile in the parent folder, it will ask for the directory where the file is located.

[patrikg]

Have you seen this:
https://code.google.com/archive/p/tcztools/

[red]

Have you seen this:
https://code.google.com/archive/p/tcztools/

No, i haven't but i looked at it, and it appears to be a commandline tool. I created this project to be a automatized, interactive tool for creating TCE extensions.

[aw]

Can you put your code up on github or something? Thanks

[bmarkus]

No, i haven't but i looked at it, and it appears to be a commandline tool. I created this project to be a automatized, interactive tool for creating TCE extensions.

Isn't 'automatized, interactive' a contradiction?

[red]

No, i haven't but i looked at it, and it appears to be a commandline tool. I created this project to be a automatized, interactive tool for creating TCE extensions.

Isn't 'automatized, interactive' a contradiction?

I meant, it can have an interactive and an automatic (terminal) mode.