Generated content is only "extern(C):".

[repeatedly]

Generated content is only "extern(C):".

[jacob-carlborg]

I've update the readme file. What exactly is the problem when you run dstep, no output?

[jacob-carlborg]

I assume you've compiled this from source. Does the pre-compiled binary work?

[repeatedly]

@jacob-carlborg
Yes, the problem is no output.
The content of generated .d file is only 'extern(C):'.

I didn't know the pre-compiled binary.
I tried the pre-compiled binary for Mac, it works fine!
This is a big help :)

[jacob-carlborg]

That's good to hear. But I'm still interested in figuring out way it didn't work when you compiled from source. Did you try any of the other test files?

[repeatedly]

Yes, other test_files and C header too.

I will try updated README process later.

[lomereiter]

I'm stuck with the same problem, although I swear I had dstep working successfully on the same codebase just a couple of years ago (many thanks for that!)

I'm using Linux and have tried all sorts of clang/dstep version combinations to no avail.
To reproduce, clone https://github.com/lomereiter/htslib, install libclang, and run

cd htslib/
CLANG_VERSION=3.8
DSTEP_BIN=../../dstep/bin/dstep # tweak dstep/clang paths as needed
export LD_LIBRARY_PATH=/usr/lib/llvm-${CLANG_VERSION}/lib
${DSTEP_BIN} --comments=false -I. -Icram/ -Ihtslib/ \
  -I/usr/include/clang/${CLANG_VERSION}/include/ cram/cram.h -o htslib.d; ls -l htslib.d

I would hope for some kind of an error message at least, but all I get is extern(C): as the output.

[ciechowoj]

Yeah, I reproduced the issue, so it isn't only your setup.

[ciechowoj]

Ok, so the problem is "cram/cram.h" contains only include files, and no declarations and dstep translates only the content of the exact input file and nothing else. In your case you need to fuse those files into single file of execute dstep for every file separately (I think there is option to execute dstep at the whole directory at once, or maybe not)...

[jacob-carlborg]

Ok, so the problem is "cram/cram.h" contains only include files, and no declarations and dstep translates only the content of the exact input file and nothing else

Yes, that makes sense.

In your case you need to fuse those files into single file of execute dstep for every file separately (I think there is option to execute dstep at the whole directory at once, or maybe not)...

It's possible to run DStep on a whole directory (with master). I would recommend doing that instead of merging the header files. Then manually create a single file with public imports, if necessary.