From: Darrick H. <dha...@dj...> - 2007-03-16 15:02:09
|
Kristian Kielhofner wrote: >> I'm really tempted to make a proper VMware development environment so >> I can say definitively that my environment isn't at fault. Maybe stick >> that into the SVN repository as well? >> > > While many people use VMWare, that really defeats the purpose of > buildroot. trunk now includes a basic dependency check. I plan on > extending that to check the host system for all of the various > required software components, versions, etc. That should drastically > cut down on some of the problems people are having. > There are several reasons to use VMWare. The best reason is to prevent accidental mishaps. This will go away with some of the changes in trunk, but currently, the makeimage.sh script must be run as root. I know I've accidentially stayed as root and done some actions which could potentially cause problems to the host system. Again, most of that risk will go away with trunk shortly. Kristian has started using a method of making the images that doesn't require the user to be root. (I believe this involves fakeroot). The other reason for using vmware is to have a consistent build environment. Most, if not all, of the development work has been done on CentOS4. If someone doesn't have a spare PC around, they could setup a VMware image with CentOS in it (just for consistency). However, it shouldn't matter which version of Linux you compile this on, as long as the basic system requirements are met. > How would we stick a VmWare image into SVN? > That would be absurd. The host system requirements don't change often enough to require revision control. (let along the size of the creature). I don't think we need to distribute a virtual machine for the build environment. It would be good to have the build system requirements documented better. Perhaps we need a wiki other than voip-info--the information gets too muddled there. Darrick -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com |