Boost logo

Boost-Build :

From: Ralf W. Grosse-Kunstleve (RWGK_at_[hidden])
Date: 2002-06-06 16:10:57

> Please be specific about what you mean.
> Where is the replication?

Here (from the mipspro-tools.html):

MIPSPRO_BIN_DIRECTORY Path to bin directory of compiler excutables. $(MIPSPRO_ROOT_DIRECTORY)/bin
MIPSPRO_STDLIB_DIRECTORY List of directories containing the standard libraries. $(MIPSPRO_ROOT_DIRECTORY)/lib32/mips3

The same information is encoded in the cc, CC and ld front-end
scripts. Only, these scripts adjust the pathnames correctly depending
on the combination of -32, -n32, -n64, -mips1, -mips2, -mips3, -mips4,
and depending on the kernel you are running (there are 32-bit and
64-bit IRIX kernels).

The Linux toolset, as one example, is highly tailored for the target
environment and works very well there. My point is that IRIX is
different, and what makes sense under Linux does not necessarily make
sense under IRIX. E.g., I think it is not even possible to install
multiple versions of CC and cc without doing very weird things, and the
end-user commands are always in /usr/bin. If that is not in your path,
you are lost anyway. Therefore I come to the conclusion that under IRIX
it is best to fully rely on the environment (for PATH) and the
front-end scripts. On the other hand, the toolset should have a
provision that allows the user to easily switch between -n32, -n64, etc.

> So are you also saying that there isn't a standard script one can run to
> setup mipspro that comes with the compiler setup? This is how some of the
> other toolsets work.

Under IRIX you take for granted the cc, CC and ld are provided by the
OS. These components are installed with the same tool (inst) that is
used for installing the rest of the OS. I have never seen an option
for changing the target locations.



Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at