-----Original Message----- From: demetrioussha...@netscape.net Cc: rc7...@yahoo.com Sent: Sat, 21 Feb 2009 2:33 pm Subject: Re: [oss-devel] Porting to other OS's Thanks for the info, however, our OS isn't quite ready to be announced yet, so I can't really talk about it at this point. When the time comes, you'll know who we are. There are many other things that we'll have to maintain, since we're a very small team. With that being the case, it would make more sense to port over OSS, than to port/write sound drivers one by one. Dee Sharpe -----Original Message----- From: François Revol <re...@free.fr> To: Discussion mailing list for developers of OSS <oss-devel@mailman.opensound.com> Sent: Sat, 21 Feb 2009 20:54:06 +0100 CET Subject: Re: [oss-devel] Porting to other OS's > > Thanks for your response.? I was hoping to catch the attention of > someone > on the opensound development team.? What exactly are > setup/gen_driver_<os>.inc & It is included in the setup code, built and ran by the build system to generate parts of each driver that include their PCI vendor/device ID and settings table. > setup/srcconf_<os>.inc supposed to do.? What I mean is, what's the > specifics of what they're doing? This one is used to fix some build settings depending on the arch. For example the BeOS code maps the "BePC"=2 0uname arch to x86 since it's non standard. Depending on your OS you might have to fake the uname() calls I suppose. What is it you intend to port OSS to ? François. _______________________________________________ oss-devel mailing list oss-devel@mailman.opensound.com http://mailman.opensound.com/mailman/listinfo/oss-devel A Good Credit Score is 700 or Above. See yours in just 2 easy steps!
_______________________________________________ oss-devel mailing list oss-devel@mailman.opensound.com http://mailman.opensound.com/mailman/listinfo/oss-devel
