Hi well as far as I know the prefix parameter of the configure script defines the folder where the program which gets build is supposed to be installed. So I mean where it is supposed to run and execute. E.g. we pass a prefix like /home/fritz/newprog then the program gets installed to that folder and runs within that location. That means it expects all its configuration files which it needs perpended with that prefix. Ok so far no problem. But let's say we do a cross compile. In this case the prefix parameter defines the location where the program will be located and run on the target machine? But the build-system I'm using at the moment uses prefix to specify the location of the toolchain on the host. E.g. --prefix /opt/devel/arm7/ But as a result of this, the produced software expects its runtime environment in the folder /opt/devel/arm7 on the target machine. So any configuration file needed by the app, is perpended with /opt/devel/arm7/. So I'm sort of confused with the prefix parameter in the context of cross compiling. So in my opinion it' more logical to specify with (make DEST_DIR="/opt/devel/arm7" install) the location of the produced app on the host - temporary until it gets copied to the target. And the parameter prefix should be filled with something like: /usr/local (depending on the location where the app gets copied on the target system) Thanks. -- Regards, --Codefritz -- Regards, --Codefritz _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
