All of lore.kernel.org
 help / color / mirror / Atom feed
From: "lode leroy" <lode_leroy@hotmail.com>
To: grub-devel@gnu.org
Subject: Re: problems compiling NTFS on GRUB2
Date: Mon, 16 Aug 2004 11:22:29 +0200	[thread overview]
Message-ID: <BAY22-F32ogxLDp7mvj0004bfc8@hotmail.com> (raw)

>Ok.  But I assume you have to add something in order to link it to the 
>library?
ah, yes indeed...

+ grub_setup_LDFLAGS = libntfs.a

+ grub_emu_LDFLAGS = libntfs.a

  ntfs.mod: pre-ntfs.o mod-ntfs.o
      -rm -f $@
-      $(LD) -r -o $@ $^
+      $(LD) -r -o $@ $^ libntfs.a
       $(STRIP) --strip-unneeded -K grub_mod_init -K grub_mod_fini -R .note 
-R .comment $@

Would you have suggestions on compile flags needed to compile libntfs
for grub? (now they are -g -O2 -MT -MD -KP -MF )

>I don't think it is easy and clean to use libntfs.

I figure that libntfs was intended to be " a library to avoid code 
duplication
and provide access to NTFS to other GPLed programs " therefore
I assume that using this effort would result in the better solution.

>But the best way to implement NTFS is by writing it yourself.  It is
>on my todo already, or do you want to do this?

I have no intention whatsoever to implement an ntfs driver... providing
the glue between grub and libntfs is/should be a much smaller effort...
Unless you're telling me trying to do this is a lost effort?

>Another thing to consider is its size.
ntfs.mod is 74KB . I don't thinks thats insurmountable...

-- lode

_________________________________________________________________
Don't just search. Find. http://search.msn.be




             reply	other threads:[~2004-08-16  9:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-16  9:22 lode leroy [this message]
2004-08-16  9:44 ` problems compiling NTFS on GRUB2 Marco Gerards
2004-08-16 10:35   ` Yoshinori K. Okuji
  -- strict thread matches above, loose matches on Subject: below --
2004-08-13  6:59 lode leroy
2004-08-13 10:25 ` Marco Gerards
2004-08-12 12:43 lode leroy
2004-08-12 13:02 ` Marco Gerards

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BAY22-F32ogxLDp7mvj0004bfc8@hotmail.com \
    --to=lode_leroy@hotmail.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.