how to add local changes to buildworld?

Daniel Braniss danny at cs.huji.ac.il
Wed Mar 28 05:51:04 UTC 2018



> On 27 Mar 2018, at 19:47, Ian Lepore <ian at freebsd.org> wrote:
> 
> On Tue, 2018-03-27 at 19:20 +0300, Daniel Braniss wrote:
>> Hi,
>> I have some local additions which int the past, after making changes
>> to some Makefiles, etc, I got them compiled
>> but somehow, things stopped working after 11, so I’m now trying to do
>> a fresh set of patches,
>> and was wondering if there is some docs around on how to to this
>> cleanly? trying to figure out the *.mk is becoming a bit complicated.
>> thanks,
>> 	danny
>> 
> 
> If you're asking what I think (you want to add code of your own into
> the buildworld), just add LOCAL_DIRS="path/to/dir1 path/to/dir2" to the
> buildworld command line and it will visit your directories and run the
> same targets there as for standard freebsd dirs (so your makefiles have
> to have those targets, mostly easily accomplished by including the
> usual bsd.<foo>.mk where foo=prog|lib|subdir|whatever.
> 
> The local dir paths in LOCAL_DIRS must be relative to the top-level
> freebsd source dir, you can't use absolute paths (but you can use
> relative paths that take you outside the freebsd path, I think, like
> ../mysources/project1).
> 
> -- Ian
> 
I guess in my haste I was not clear enough :-)
my problem is the dependency,
in particular, it’s a pam module, that needs a local library. in the past the library was compiled first, and then the module,
now it still happens, but the module does not find the library, which has been compiled! there is a new piece of mail that
i’m missing :-( 
i’ll try again with LOCAL_DIRS.
thanks
	danny



More information about the freebsd-hackers mailing list