Greetings! This message is mainly (but not exclusively) for Papiosaur:

In the process of resurrecting my neglected ECX fork called EEC (AmigaE compiler), I'm planning on extracting the PPC and 68k backends to shared libraries to make the compiler more modular and maintainable. The compiler executable will depend on external libraries to do anything at all. As such, I need to maintain every backend as a shared library dependency but also note that most backends will be cross-compilers.

This leads me to the next problem: Easy2Install has its own package format that I'm not familiar with. I also need to support 68k and OS4 package formats as well. If there isn't a documented format to generate, I need to write a generator script for each package format. Also, I see in the current Easy2Install readme that Installer scripts are part of the install process. How does that affect the package format?

TLDR
Mainly what I want to know is: Where is the Easy2Install package creation information?

EDIT
I forgot to mention that I have Hollywood 9 if that helps.

[ Edited by Samurai_Crow 24.07.2025 - 07:13 ]

Hi Samurai_Crow,

The packages are just simple LHA archives.

Easy2Install just extract LHA archives to a predefined destination.

On the server, i indicate to Easy2Install what sort of archive is.

with executable, without executable, with installer script generally.

There is a specific codification for the name of archive, name of drawer and name of executable if exists.

Example:

Title_1.0.lha as archive name
Title as drawer name
Title as executable name or Title-install for installer script (or just Install)

Normally all is in the Readme but maybe not all...

There are specific archives containing source code:

Title-1.0.lha as archive name
Title-10 as drawer name

I guess what I really wanted to know was: Do I need to do anything special to make interdependent packages beyond the README files in the MorphOS Storage upload?

Quote:
Sorry, i understand the term "to make interdependent packages"

EEC is going to move its code generation to a "codegen.library" containing optimizer code, a MorphOS ABI library and a PowerPC library doing the actual code generation. Optional other libraries will include 68020 based AmigaOS HUNK libraries for cross-development. How do I make sure it gets the library packages it needs?

[ Edited by Samurai_Crow 25.07.2025 - 04:37 ]

EasyInstall is not a package manager like linux, EasyInstall will not search dependencies for a specified program, it's the user who must do the installation of different parts.

Thanks!

Quote:
Use Grunch. Ask for your own database from Geit, or create an entry and I'll add it to my RNO database, for example.