There is a libafs_tree target which builds a libafs_tree directory.
The libafs_tree is a purely source directory (with its own configure
script) that can be packaged up for distribution.
The normal build process will still build kernel modules as before.
The libafs_tree is NOT built by default.
-derek
"Neulinger, Nathan" <[EMAIL PROTECTED]> writes:
> Is the entire libafs build going to be split out into a separate configure,
> or is this going to be a duplicated libafs-only configure target?
>
> Would be nice to see some more public communication on what the plans are
> with some of these changes... haven't really seen any mention of what they
> are for.
>
> -- Nathan
>
> ------------------------------------------------------------
> Nathan Neulinger EMail: [EMAIL PROTECTED]
> University of Missouri - Rolla Phone: (573) 341-4841
> Computing Services Fax: (573) 341-4216
> _______________________________________________
> OpenAFS-devel mailing list
> [EMAIL PROTECTED]
> https://lists.openafs.org/mailman/listinfo/openafs-devel
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
OpenAFS-devel mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-devel
