General TC > Programming & Scripting - Unofficial

Easy and fast way to create or update extensions

<< < (2/4) > >>

Jakob Bysewski:
Yeah, squashfs is needed, too.

The *.dep file is to be created by the user, as it's content is not to be guessed easily. Do you have a proposal for automating this? We could seperate TCEs into TCEbuild and TCErun and then generate the *.dep from that.

What do you want to do with a fltk program? Currently I thought of this Makefile to help developers and packagers create extensions and to track the build of extensions for easy rebuild or update. As these things often need you to get your hands "dirty" (-> do some configuration or testing on the console) I have not thought about a graphical interface. The only thing I can think of currently is the creation of the *.info file, but for this task every text editor will be sufficient.
But if there would be a demand, this is certainly possible. Another possibility would be to automatically invoke a text editor,

Are there any other opinions to this prototype / idea?
Could this be interesting to the tc lead or the extension creaters in the community?
What other features would you like to have or which would make you use it?
As I have seen some have downloaded the Makefile without any comment  ::)

maro:
Quick question: How do you suggest to handle the split-up of the build result into multiple extensions?

For example to keep with the general intention of TC very often the documention gets seperated into a 'EXT-doc.tcz', likewise for 'EXT-locale.tcz' or 'EXT-dev.tcz.

vinnie:
ok, you're right, I was  too excited  ;D
However thought  TCES related only to the  build dependencies and not to the starting dependencies (This is why  I wrote only SDL-dev, in teory SDL_gfx is not necessary whereas what INSTALL.txt says).
I think it's a good idea to separate them, there is also more clearly.

For the fact  that there are no feedback, perhaps  in the forum are all professional users, but for people like me this makefile is a good thing  ;)

Jakob Bysewski:
@maro:
This is something to think about in depth but I think it'll be needed if this process of creating extensions should be widely adapted.
It think it should be possible to specify subfolders as variables which then could be automatically seperated - e.g. DOC_DIR=/usr/local/share/doc/EXTNAME/
As this is similar for most packages one could make defaults which would only have to be changed for some packages.

My goal is to make building extensions feasible (so that everyone can make a new extension when he/she wants a specific package without even knowing in detail how to compile from source), easy to maintain and maybe even fully automated - last but definitivly not least the extensions built with this method should stand all tc requirements and fullfill them out of the box.

What do you think about this approach? I'll try to get to this tomorrow.

@vinnie:

--- Quote ---However thought  TCES related only to the  build dependencies and not to the starting dependencies.

--- End quote ---
Uhm, I think I have chosen the wrong formulation - these are in deed only the build dependencies and no *.dep file is created automatically.

vinnie:
uhm, in teory for circuslinux  should be enough the sdl-dev dependence.
Sdl need it only to start..

Navigation

[0] Message Index

[#] Next page

[*] Previous page