Question about building iPXE with named configuration
|
2018-08-16, 15:36
(This post was last modified: 2018-08-16 15:38 by pxe_curious.)
Post: #1
|
|||
|
|||
Question about building iPXE with named configuration
I have been building iPXE undionly.kpxe and snponly.efi binaries for a while now.
There are some features I need that are not in the default build and some features I really do not need. To get the build I want, I have been modifying the console.h and general.h files in the src/config folder. I have to really keep two sets of the general.h file, one for PCBIOS and one for EFI. I realized from the get-go that my manual workaround for this is cumbersome but didn't think to check if there is a better way to do this. I recently saw the named_config article but am not really sure how to use it, though I think this would solve my issue. My question specifically then is: Should I copy the edited versions of console.h and general.h files into a named folder into the src/config/local folder and leave the originals untouched? Or is it sufficient to place respective text files with just the changed lines in the named local folder? Would I need to add an explicit #undef for features I do not want? |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
Question about building iPXE with named configuration - pxe_curious - 2018-08-16 15:36
RE: Question about building iPXE with named configuration - NiKiZe - 2018-08-16, 17:55
RE: Question about building iPXE with named configuration - pxe_curious - 2018-08-16, 19:19
RE: Question about building iPXE with named configuration - NiKiZe - 2018-08-16, 20:01
RE: Question about building iPXE with named configuration - pxe_curious - 2018-08-16, 21:39
RE: Question about building iPXE with named configuration - NiKiZe - 2018-08-16, 21:41
RE: Question about building iPXE with named configuration - pxe_curious - 2018-08-16, 22:32
|
User(s) browsing this thread: 1 Guest(s)