From: Corentin Chary <corentin.chary@gmail.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH 1/2] mkfs.ubifs: UBI I/O Library
Date: Fri, 8 May 2009 22:32:18 +0200 [thread overview]
Message-ID: <71cd59b00905081332j69ca911fndb112fe31eeec37e@mail.gmail.com> (raw)
In-Reply-To: <8bd0f97a0905081325m1d70f040ubb3b2a6ac8f63c05@mail.gmail.com>
I didn't think of calling make here.
Thanks
On 5/8/09, Mike Frysinger <vapier.adi@gmail.com> wrote:
> On Fri, May 8, 2009 at 15:41, Corentin Chary wrote:
>> On Fri, May 8, 2009 at 8:58 PM, Mike Frysinger wrote:
>>> On Fri, May 8, 2009 at 10:59, Corentin Chary wrote:
>>>> I'll see what I can do to use libubi the way I want.
>>>> The problem of using libubi in mkfs is not the includes (we can copy
>>>> the headers in /include or add -I../ubi-utils/include).
>>>
>>> why do you need to copy any files ?
>>>
>>>> The main problem is that ubi-utils/Makefile make a libubi.a but
>>>> mkfs.ubifs/Makefile have no way to use it
>>>
>>> what's wrong with adding -lubi and a -L path ?
>>
>> It'll work only if libubi is already built. You can fix that in the
>> root Makefile, but
>> - parallel builds may not work (make -j)
>
> a simple dependency is easy
>
>> - "cd mkfs.ubifs && make" won't work (using only the mkfs.ubifs Makefile)
>
> if the .a file is added to the dependency list, then it's easy to have
> a normal recursive target:
> ........./libubi.a:
> $(MAKE) -C $(dir $@)
> -mike
>
--
Corentin Chary
http://xf.iksaif.net
next prev parent reply other threads:[~2009-05-08 20:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 10:21 [PATCH 0/2] mkfs.ubifs and libubiio Corentin Chary
2009-05-07 10:21 ` [PATCH 1/2] mkfs.ubifs: UBI I/O Library Corentin Chary
2009-05-07 10:21 ` [PATCH 2/2] mkfs.ubifs: format directly ubi volume using libubiio Corentin Chary
2009-05-08 8:49 ` [PATCH 1/2] mkfs.ubifs: UBI I/O Library Artem Bityutskiy
2009-05-08 12:07 ` Corentin Chary
2009-05-08 12:20 ` Artem Bityutskiy
2009-05-08 13:58 ` Corentin Chary
2009-05-08 14:06 ` Artem Bityutskiy
2009-05-08 14:14 ` Artem Bityutskiy
2009-05-08 14:59 ` Corentin Chary
2009-05-08 18:58 ` Mike Frysinger
2009-05-08 19:41 ` Corentin Chary
2009-05-08 20:25 ` Mike Frysinger
2009-05-08 20:32 ` Corentin Chary [this message]
2009-05-08 20:36 ` Mike Frysinger
2009-05-07 11:59 ` [PATCH 0/2] mkfs.ubifs and libubiio Corentin Chary
2009-05-07 12:57 ` Josh Boyer
2009-05-07 13:29 ` Corentin Chary
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=71cd59b00905081332j69ca911fndb112fe31eeec37e@mail.gmail.com \
--to=corentin.chary@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=vapier.adi@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox