module opt_* building

From: John-Mark Gurney (gurney_j_at_efn.org)
Date: 07/21/03

  • Next message: Terry Lambert: "Re: *statfs exposure of file system IDs to non-root users" 
    Date: Mon, 21 Jul 2003 01:08:36 -0700
To: arch@FreeBSD.org

    I recently realized that for kernel module building, we can simply create
    a symlink pointing to the opt_*.h file created by config. (See attached
    patch.)

    This only is part of the work. The problem is that the modules/Makefile's
    define a target, which needs to be overriden in the case of being built
    as part of the kernel, and left intact when building standalone.

    The only thing I can think of is to add a opt_xxx.h_def or something
    similar to the target in the modules/Makefile, and then add a dependancy
    on that target in the standalone case.

    I have thought about a way to automate building of these options. It'd
    require setting up a file with defaults to build from. Extending options
    files? Yet another place to list options doesn't seem like a good idea.

    Comments? 

    -- 
  John-Mark Gurney				Voice: +1 415 225 5579
     "All that I will do, has been done, All that I have, has not."

    _______________________________________________
    freebsd-arch@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-arch
    To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"

  • Next message: Terry Lambert: "Re: *statfs exposure of file system IDs to non-root users"