[m-users.] Installing a subset of built grades

Julien Fischer jfischer at opturion.com
Wed May 29 16:18:17 AEST 2013

On Wed, 29 May 2013, Peter Wang wrote:

> On Wed, 29 May 2013 15:12:59 +1000 (EST), Julien Fischer <jfischer at opturion.com> wrote:
>> On Tue, 28 May 2013, Mark Green wrote:
>> > I'm currently having some problems compiling the non-native grades of
>> > Mercury13.03 on MingW, but the native grades compiled fine (after the
>> > first failure I was able to used the successfully installed native
>> > grades to bootstrap the next attempts).
>> By, "non-native", I assume you mean the non-C grades?  What were the
>> problems you encountered?
>> > However whenever I try to do the install again, the make script
>> > insists on building all of the already-existing native grades, and
>> > then goes to install them, generating nothing but a series of
>> > "<filename> is unchanged" messages but having spent an hour or more
>> > building the grade.  Is there any way to tell the installer which
>> > grades to install without reconfiguring the project, or to tell it not
>> > to install grades that have already been installed successfully?
>> No.  (If you're feeling brave you can hack some Mmakefiles and, after
>> installation, edit Mercury.config to conform with any changes, then
>> in most circumstances it's possible.)
> mmake install_grades LIBGRADES=blah
> To avoid building and installing the compiler itself you can edit the
> "install_grades: install_main" line in Mmakefile.

Plus, then update the lists of library grades in the installed version
of Mercury.config.  (Arguably, we should get rid of variable and just
get the compiler to scan for the presence of .init files in the library
installation directory in order to determine what grades are installed.)


More information about the users mailing list