Ticket #29 Automate the build system, software part - Page 1

https://trac.godzil.net/gcc4ti/ticket/29

TIGCC's build scripts have at least two characteristics which make them, in their current state, less than satisfactory for packaging (and therefore, making releases on a regular basis...):
* they compile and install at the same time (a common practice with make, ant, mvn and other build systems is to separate those goals);
* they install under /usr/local/tigcc, instead of a more standard prefix such as /usr/share/tigcc.

Using a unified, advanced build system, may be overkill for our purposes, since sh/bash/perl scripts, or a set of Makefiles + sh/bash/perl scripts, may do the job just fine. Let's discuss that... and work on fixing this ticket.

NOTE: it's thought that unifying the "tigcc" and "tigcc-linux" modules ( https://trac.godzil.net/gcc4ti/ticket/26 ) will help fixing this ticket.

GCC4TI should install to */gcc4ti, not */tigcc!

Improving the buildability applies to both TIGCC and GCC4TI, but in case you hadn't noticed,

TIGCC's build scripts have at least two characteristics which make them, in their current state, less than satisfactory for packaging (and therefore, making releases on a regular basis...):
* they compile and install at the same time (a common practice with make, ant, mvn and other build systems is to separate those goals);* they install under /usr/local/tigcc, instead of a more standard prefix such as /usr/share/tigcc.

only mentioned TIGCC's build scripts (specifically, what's wrong with the current state of them).

Let's also mention that GCC4TI's Windows installer defaults to installing in "C:\Program Files[b]GCC4TI[/b]". Of course, users are free to install GCC4TI over TIGCC, just as they're free to install TIGCC over GCC4TI.

I know you can do better, more constructive posts than ./2

I won't discuss TIGCC's future in a GCC4TI forum.

And as I already wrote in another thread somewhere else on yAronet, the correct install location for a cross-compiler according to the Fedora Packaging Guidelines is /usr/target. That's when it's packaged in the distribution. Installation by the user goes to /usr/local instead of /usr, and that's what build systems normally default to, so /usr/local/target fully makes sense as the upstream default. The current TIGCC RPM which uses /usr/local/tigcc will be fixed, a package should use a subdirectory of /usr, not /usr/local. So this is TIGCC's position, anything else is up to you.

And as I already wrote in another thread somewhere else on yAronet, [...]

I know that, but that thread was written in French (unsuitable for interaction with a larger community)

I won't discuss TIGCC's future in a GCC4TI forum.

Given that you hardly discuss it on the English-speaking TIGCC forum as well, where exactly do you want to discuss it ?