Re: How to reuse the the part of codes about file system in grub ?

[Andrei Borzenkov]

On Fri, Aug 7, 2015 at 1:30 PM, Arch Stack <address@hidden> wrote:
>>
>> grub-mount requires all filesystem drivers which in turn require all
>> supporting code so you cannot compile it alone.
>>
>
> I know that grub-mount depends on many part on GRUB, but not all of it,
> isn't it? I think it never need 'grub-menulst2cfg' or 'video.mod' or many
> other mod in hundreds of mods.
> What I want to know it's how Makefile works to generate grub-mount, or how
> autotools works.
>

There is no provision to selectively enable/disable individual modules
or tools. You will need to modify templates and remove parts you do
not need.

GRUB top level files are Makefile.util.def and
grub-core/Makefile.core.def. They are processed by autogen.sh to
generate Makefile.am. I'm afraid the only documentation for it is in
sources. Documenting it would be of great help.

>> Current development version of GRUB can be built on/for Windows (it
>> was tested with Cygwin, MinGW, MinGW-64 cross compiler). grub-mount
>> itself depends on FUSE so cannot be used as is on Windows (unless
>> there is FUSE port for Windows); rewriting it as Windows installable
>> file system is certainly possible and would be the best route in this
>> case. That would make it also available on Windows ... as long as you
>> are content with lack of write support.
>>
> I have tried to comiple GRUB on Cygwin or MSYS2 but failed.

Without knowing exact GRUB commit, Cygwin version and errors you got
it does not say anything. Post full build log starting from
autogen.sh.

>                                                                               
>            I think that it
> will only be little help with me even if it will be compiled successful.
> Because it need the environment (dll?) that Cygwin supports and it will be
> hard to make info a driver.
> However I want to know that how to compile GRUB on Cygwin. As you say ,
> grub-mount can't be used because the lack of FUSE, so it will be disable
> when compiled? Which argument will disable it? And which argument can
> disable other parts of GRUB? Where can I find that how to change the compile
> options to achieve my goal?
>
> I know that it will need a lot of things to do to achieve my goal, and I'd
> like to spend time on it. But I want to know how to do it properly.
>
> And now I have another idea: as GRUB is based on mods, can I write a mod
> loader on Windows driver to use the functions in the filesystem mods to read
> the filesystem?