Hi Vaci,

Thanks. This is a bug. It appears to have been introduced here:

https://github.com/capnproto/capnproto/commit/b0868e347e977f18e7b5ee0b3267d8efab82e3fa#r35369927

Somehow, it took this long -- more than a year since the 0.7.0 release --
for anyone to notice.

I've filed an issue:

https://github.com/capnproto/capnproto/issues/889

And made a pull request to fix it:

https://github.com/capnproto/capnproto/pull/890

-Kenton

On Fri, Oct 4, 2019 at 8:49 AM Vaci <[email protected]> wrote:

> Hi,
>
> The src-prefix flag to the Capnp schema compiler appears to be affected by
> the import-path flag in version 0.7.0:
>
> Given a schema file in the directory structure
>
> src/A/B.capnp
>
>
> *% capnp compile -oc++ --src-prefix=src src/A/B.capnp*
>
> results in the following files being generated:
>
> ./A/B.capnp.h
> ./A/B.capnp.c++
>
>
> ..however, running
>
> *% capnp compile -oc++ --src-prefix=src --import-path src/A src/A/B.capnp*
>
> the generated files lose their subdirectory structure:
>
> ./B.capnp.h
> ./B.capnp.c++
>
>
> When using version 0.6.1 of the compiler, the subdirectory ./A is
> generated in both cases.
>
> Is this behaviour change intentional?
>
> Regards,
> Vaci
>
>
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Cap'n Proto" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/capnproto/71bc3c5c-6e6b-4728-b579-c1d3a1d80db1%40googlegroups.com
> <https://groups.google.com/d/msgid/capnproto/71bc3c5c-6e6b-4728-b579-c1d3a1d80db1%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Cap'n Proto" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/capnproto/CAJouXQket2xB9fGxamuzBKtxFL7zC9bkL74zjrzv1EfhEciNaA%40mail.gmail.com.

Reply via email to