From: Rami Rosen <roszenrami@gmail.com>
To: t-pehous@microsoft.com
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Building app with source in subdirectory ?doesn't work
Date: Mon, 10 Sep 2018 12:14:14 +0300 [thread overview]
Message-ID: <CAKoUArmC+48vuG2dVzHa8vC+Xc=QZu=Qo6PbcQOcr0PUA0uroA@mail.gmail.com> (raw)
In-Reply-To: <CY4PR2101MB0866B292B4A4373CD7A11FA08C060@CY4PR2101MB0866.namprd21.prod.outlook.com>
Hi Petr,
OK, your reply clarifies the issue. I confirm that I could reproduce
the same issue
you had following your reply. So something is missing, or maybe if the
use case is justified, maybe
additional work should be done in the build system (maybe related to
mk/rte.extsubdir.mk) to support it (I assume you know the build system
is now moving to meson/ninja)
I found a workaround, maybe it will satisfy you.
I created a soft link from the helloworld folder:
ln -s tst/tst.c tst.c
and
instead having
SRCS-y := main.c \
tst/tst.c
I use
SRCS-y := main.c tst.c
And it works for me. Any change in tst/tst.c and running make triggers
building of tst/tst.c. "make clean" works, etc.
Another thing that I wan to mention that generally the build system
does support nesting
but in a different way than you try. What I mean is creating
subfolders under a sprcified folder, but not
having modules at all in the root folder.
For example, the multi process sample app:
https://git.dpdk.org/dpdk/tree/examples/multi_process
Regards,
Rami Rosen
http://ramirose.wixsite.com/ramirosen
next prev parent reply other threads:[~2018-09-10 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-09 10:51 Rami Rosen
2018-09-09 18:21 ` Petr Houska
2018-09-10 9:14 ` Rami Rosen [this message]
2018-09-10 16:47 ` Petr Houska
-- strict thread matches above, loose matches on Subject: below --
2018-09-09 4:49 Petr Houska
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='CAKoUArmC+48vuG2dVzHa8vC+Xc=QZu=Qo6PbcQOcr0PUA0uroA@mail.gmail.com' \
--to=roszenrami@gmail.com \
--cc=t-pehous@microsoft.com \
--cc=users@dpdk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).