include_src ok but what about include_include ?

[opensam]

Hello,

I'm new to relx. It seems cool. Thanks.
I've {include_src, false}. in my relx config.
After building the release the "src" directory and its content are not included as expected.
I have also {i, "include"} in erl_opts in rebar.config . After building the release the "include" directory and its source content is packaged in the release. I didn't expect that as I think included src is src.
Is this an issue with {include_src, false} ?

Have fun

[opensam]

Gentle bump. Any thoughts about not including "include" when not including "src" ?

[tsloughter]

@ericbmerritt what do you think?

[ericbmerritt]

@opensam in general the 'include' directory is where you put your public include files. That is, the include files that must be available to work with your library. If you are publishing something that is not designed to be a library, the include directory should be empty. This comes down to the expected use of that directory.

It is expected that you will put private include files (those you use internally for your app) into the src directory with the rest of your source files. Your public include files, those that are part of your API go in the include directory.

With that in mind if we didn't include the 'include' directory, even when the src directory is excluded, we would break things.

[opensam]

Thank you for explaining. I think my (private) "include" is badly located and I should move it to "src/include".
Thanks Tristan & Eric.