demetrioussha...@netscape.net wrote: > 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 & setup/srcconf_<os>.inc supposed to do. > What I mean is, what's the specifics of what they're doing? srcconf_<os>.inc contains the check_sysdep() function that is called in the beginning of srcconf.c. It has opportunity to change some fields in the conf structure (if necessary). This function can be empty.
gen_driver_<os>.inc contains the generate_driver() function that will be called once for each directory in kernel/drv/. This function has responsibility to generate <driver>_cfg.h (contains some macros and include statements used by the source files) and <driver>_cfg.c that contains any OS dependent driver module initialization code. The srcconf.c program uses the conf structure to hold parameters. This structure is initialized in the beginning of srcconf.c and the check_sysdep() function can do some adjustments. Later the .config files in each directory of OSS sources contain definitions that override the initial values. All this is operating system dependent. The only requirement is that generate_driver() creates the above two files. You can take a look at the existing files for the other operating systems. Finally there are two ways to compile OSS. The first way (used by Solaris) is to compile everything in the development system and then to ship only binaries to the client/target system. The second way requires that some "stub" code (<driver>_cfg.c) is compiled in each target system at the time when OSS is installed. For example Linux doesn't have proper kernel module interface so all modules need to be built on-site. Best regards, Hannu _______________________________________________ oss-devel mailing list oss-devel@mailman.opensound.com http://mailman.opensound.com/mailman/listinfo/oss-devel
