Thread: iLiad Proposed iLiad Packaging/Installation Standard
View Single Post
Old 04-27-2007, 01:50 PM   #20
nekokami
fruminous edugeek
nekokami ought to be getting tired of karma fortunes by now.nekokami ought to be getting tired of karma fortunes by now.nekokami ought to be getting tired of karma fortunes by now.nekokami ought to be getting tired of karma fortunes by now.nekokami ought to be getting tired of karma fortunes by now.nekokami ought to be getting tired of karma fortunes by now.nekokami ought to be getting tired of karma fortunes by now.nekokami ought to be getting tired of karma fortunes by now.nekokami ought to be getting tired of karma fortunes by now.nekokami ought to be getting tired of karma fortunes by now.nekokami ought to be getting tired of karma fortunes by now.
 
nekokami's Avatar
 
Posts: 6,745
Karma: 551260
Join Date: Oct 2006
Location: Northeast US
Device: iPad, eBw 1150
Quote:
Originally Posted by Adam B.
You know, I've wondered how that would work if you specified ./configure --prefix=$CURRENTDIR. I always assumed it would take whatever was in the CURRENTDIR envrionment variable when you ran the configure script.

Most programs you don't have to worry about where they are compiled for because `make install` puts everything where it needs to be.
Could we somehow incorporate make install as part of the ipkg script wrapper?
nekokami is offline   Reply With Quote