Page MenuHomeFreeBSD

config.mk: Add MK_VIMAGE knob
ClosedPublic

Authored by stevek on Apr 18 2023, 3:28 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Apr 27, 2:32 AM
Unknown Object (File)
Fri, Apr 19, 1:01 PM
Unknown Object (File)
Tue, Apr 9, 8:38 PM
Unknown Object (File)
Dec 23 2023, 1:55 AM
Unknown Object (File)
Nov 8 2023, 6:08 AM
Unknown Object (File)
Oct 7 2023, 4:56 AM
Unknown Object (File)
Jun 19 2023, 8:28 PM
Unknown Object (File)
Jun 16 2023, 3:52 AM

Details

Summary

Default to VIMAGE as yes.
Add VIMAGE to __DEFAULT_DEPENDENT_OPTIONS (to define VIMAGE_SUPPORT)

Only output VIMAGE to opt_global.h when VIMAGE support is wanted.

Obtained from: Juniper Networks, Inc.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision was not accepted when it landed; it landed in state Needs Review.Tue, Apr 9, 5:08 PM
This revision was automatically updated to reflect the committed changes.

What is the value of MK_VIMAGE_SUPPORT over MK_VIMAGE? We now have an unused MK_VIMAGE. What will it control?

This commit is missing an addition of tools/build/options/WITHOUT_VIMAGE and WITHOUT_VIMAGE_SUPPORT and breaks GitHub CI because makeman spots the missing files.

sys/conf/kern.opts.mk
187

This can't possibly work. There's no opt_vimage.h, so this just throws errors.

What is the value of MK_VIMAGE_SUPPORT over MK_VIMAGE? We now have an unused MK_VIMAGE. What will it control?

This commit is missing an addition of tools/build/options/WITHOUT_VIMAGE and WITHOUT_VIMAGE_SUPPORT and breaks GitHub CI because makeman spots the missing files.

Good point. I think just having a MK_VIMAGE would be sufficient to control the VIMAGE define in the opt_global.h