On 2018-03-21 17:06, Russel Winder wrote:
No I wasn't. And it works a treat.
Cool :). I recommend having a look at the changelog and the usage
information (--help).
--
/Jacob Carlborg
On Tue, 2018-03-20 at 22:08 +0100, Jacob Carlborg via Digitalmars-d-
learn wrote:
>
[…]
> Not sure if this will help, but are you aware that DStep can add a
> package to the module declaration using "--package"?
No I wasn't. And it works a treat.
--
Russel.
On 2018-03-19 18:29, Russel Winder wrote:
I had assumed that a directory of modules was a package. So for
example:
A/a.d
A/b.d
were two modules in package A. Especially given there is a module
statement at the beginning of each module:
A/a.d has module A.a;
A/b.d has module A
On Mon, 2018-03-19 at 11:56 -0600, Jonathan M Davis via Digitalmars-d-
learn wrote:
>
> […]
> Well, what's the module statement in linux_dmx.d look like?
>
There wasn't one, even though I knew there was one.
--
Russel.
===
Dr Russel Winder t: +44 2
On Mon, 2018-03-19 at 17:49 +, Adam D. Ruppe via Digitalmars-d-
learn wrote:
> […]
>
> Odds are, linux_dmx.d is missing the `module
> libdvbv5_d.linux_dmx;` line.
>
[…]
You are right. I was certain I had correct module statements in all the
modules, but I hadn't.
--
Russel.
==
On Monday, March 19, 2018 17:29:10 Russel Winder via Digitalmars-d-learn
wrote:
> I had assumed that a directory of modules was a package. So for
> example:
>
> A/a.d
> A/b.d
>
> were two modules in package A. Especially given there is a module
> statement at the beginning of each module:
>
>
On Monday, 19 March 2018 at 17:29:10 UTC, Russel Winder wrote:
I had assumed that a directory of modules was a package. So for
example:
[...]
On Monday, 19 March 2018 at 17:29:10 UTC, Russel Winder wrote:
To my amateur eyes, first command-line build looks like a linking
of object files into
On Monday, 19 March 2018 at 17:29:10 UTC, Russel Winder wrote:
Especially given there is a module statement at the beginning
of each module:
It is not especially, it is ONLY because of the module statement.
The directory layout is a convention so tools can find the module
file, but only the m
I had assumed that a directory of modules was a package. So for
example:
A/a.d
A/b.d
were two modules in package A. Especially given there is a module
statement at the beginning of each module:
A/a.d has module A.a;
A/b.d has module A.b;
Now A.b needs to access something from
