DPDK usage discussions
 help / color / mirror / Atom feed
From: Petr Houska <t-pehous@microsoft.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Building app with source in subdirectory ?doesn't work
Date: Mon, 10 Sep 2018 16:47:52 +0000	[thread overview]
Message-ID: <MWHPR2101MB0875E9F433AB6E379B6BB7E68C050@MWHPR2101MB0875.namprd21.prod.outlook.com> (raw)
In-Reply-To: <CAKoUArmC+48vuG2dVzHa8vC+Xc=QZu=Qo6PbcQOcr0PUA0uroA@mail.gmail.com>

Hi,

> 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)

It would be really beneficial for (I suppose not only) our use case where we generate some files (.c and .h) for serialization/deserialization (we're using thrift) and would prefer them contained in a standalone folder. 

Having it in standalone folder makes a few things easier. It clearly communicates that these are compiler generated files. It also makes regenerating / clearing them easy and safe.

And I don't think that's the only usecase for having modules both in project's root and a subfolder.

> 
> 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.

Awesome! That's better than the hack workaround I came up with.



  reply	other threads:[~2018-09-10 16:47 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
2018-09-10 16:47     ` Petr Houska [this message]
  -- 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=MWHPR2101MB0875E9F433AB6E379B6BB7E68C050@MWHPR2101MB0875.namprd21.prod.outlook.com \
    --to=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).