Problem specifying output directory

[allpow...@gmail.com]

Hi,

I'm testing out capnproto 0.3.0 (looks awesome!), but I'm having trouble getting the -oc++:<directory> syntax to work.

If I run:

capnp compile -oc++ Test.capnp

I get Test.capnp.c++ and Test.capnp.h in the current directory.  However, if I run:

mkdir -p build/capnp/ && capnp compile -oc++:build/capnp/ Test.capnp

I get nothing, either in the current directory or the 'test' directory.

Looking at the code, (capnpc-c++.c++:1654), I wonder how it would respect the directory parameter.  Is this a known issue?  Ideas?

Thanks,

Joshua

[Kenton Varda]

Hi Joshua,

This seems to work for me:

$ ls build/capnp

ls: cannot access build/capnp: No such file or directory

$ mkdir -p build/capnp/ && capnp compile -oc++:build/capnp/ Test.capnp

$ ls build/capnp

Test.capnp.c++  Test.capnp.h

$ capnp --version

Cap'n Proto version 0.3.0

$

Are you sure you're looking in the right place?  You mention a "test" directory, but nothing in your example seems to mention a directory with this name.

You don't see this handled in capnpc-c++.c++ because the compiler actually changes the working directory before invoking the plugin.

-Kenton

--
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 capnproto+...@googlegroups.com.
Visit this group at http://groups.google.com/group/capnproto.

[Nathan Yospe]

I found a scenario this doesn't work.

If Test.capnp is not local to the build directive, and specified with an absolute path it appears to chdir into the location of Test.capnp after the chdir into the output directory.

$ ls build/capnp

ls: cannot access build/capnp: No such file or directory

$ mkdir -p build/capnp/ && capnp compile -oc++:build/capnp/ /home/self/project/src/Test.capnp

$ ls build/capnp

$ ls /home/self/project/src/

Test.capnp Test.capnp.c++ Test.capnp.h

$ capnp --version

Cap'n Proto version 0.4.1

$

[Kenton Varda]

Hi Nathan,

This is half a bug in Cap'n Proto and half a problem with your flags.

When using an absolute path, you definitely need to use --src-prefix to tell the compiler what directory it should treat as the "root" of your source tree, for the purpose of generating output file names. This prefix will be stripped off of your file names for output purposes.

The bug in capnpc is that we don't print an error when an absolute path is given with no --src-prefix. We probably should, as it seems unlikely that anyone would actually expect or want the behavior you're seeing.

-Kenton

--

Sandstorm.io is crowdfunding! http://igg.me/at/sandstorm

[Nathan Yospe]

Hi Kenton,

Thanks for the exceptionally fast reply. Yes, that was my mistake. While the option was described in the help message, I assumed it was mostly for the purpose of specifying parallel subpaths, and didn't realize that absolute paths were unsupported.