Thanks Milan: The things we are working on would remain private. I would plan on generating them using an opensolaris machine running a ONNV installation close to what we will be running on the product. Eventually, would like to be able to cross compile them from a different machine, possibly running Linux.
As far as cc/ld flags necessary for generating the kernel modules, is that formally documented somewhere, or do I just look to ONNV modules for examples? thanks Mark > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: 2010-01-18 13:09 > To: Mark Maule > Cc: [email protected] > Subject: Re: [osol-discuss] building standalone modules > > Hi Mark, > > Mark Maule píše v so 16. 01. 2010 v 14:12 -0800: > > Not sure if this is the correct forum, so starting here: > > > > It depends of what you really need. > > > We are building a system based on opensolaris, and will be adding our > > own kernel modules. What is the precedent for building vendor-supplied > > modules? Are they generally incorporated under the os-nv src tree? My > > preference would be to build them outside the os-nv tree in order to > > avoid "polluting" the tree with vendor-specific module (and command) > > code. > > > > If you plan to keep those modules private for your company, then you can > keep them in nested workspace everywhere you want. If you plan to > integrate them later to upstream os-nv, follow os-nv tree structure, > there are several examples of modules comming from device vendors (e.g. > Intel) in os-nv gate. As for nested workspaces, Mercurial ignores > subdirectories which are not maintained by it, so you can include them > everywhere inside tree on build machines. > > Best regards, > > Milan _______________________________________________ opensolaris-discuss mailing list [email protected]
