sven.bieb...@be.thalesgroup.com wrote: > I added a remote_install option that passes a directory to install.sh. When > the directory is not specified (as in the normal "make install" or via > soundon ), the install.sh falls back to the default "/". > > This morning however, I thought of an alternative, namely to specify this at > configure time. This allows the procedure to be the same, > but requires all scripts to be adapted. OTH, specifying it at the make, > allows the same oss to be installed both on host and on target, although I > do not know if this is useful : on embedded targets the kernel is often > different and most of the time you want explicit control, which means from > the configure stage onwards different parameters passed and a separate build > directory. > > What would fit OSS best ?
While OSS doesn't officially subject itself to the GNU coding standards, doing it in any other way would just confuse user needlessly IMNSHO, so I'd propose to use the DESTDIR variable for make: http://www.gnu.org/prep/standards/html_node/DESTDIR.html Regards, Clemens _______________________________________________ oss-devel mailing list oss-devel@mailman.opensound.com http://mailman.opensound.com/mailman/listinfo/oss-devel
