www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.learn - Building custom library package with dub

reply alex1974 <alex.leisser gmail.com> writes:
I want to build a custom library with useful extensions to 
phobos. They should be named like:

extensions.regex
extensions.path
extensions.files
...

Some libraries, like extensions.files contain several files (e.g 
files.d, filesexceptions.d)

Analog to phobos I would like to import them like
import extensions.files: temporary;

What would be the best approach for the folder layout and dub?
I guess subPackages, but I can't get them to compile and link 
properly.

Thanks for the help
Mar 18
parent reply Basile B. <b2.temp gmx.com> writes:
On Saturday, 18 March 2017 at 11:29:43 UTC, alex1974 wrote:
 I want to build a custom library with useful extensions to 
 phobos. They should be named like:

 extensions.regex
 extensions.path
 extensions.files
 ...

 Some libraries, like extensions.files contain several files 
 (e.g files.d, filesexceptions.d)

 Analog to phobos I would like to import them like
 import extensions.files: temporary;

 What would be the best approach for the folder layout and dub?
 I guess subPackages, but I can't get them to compile and link 
 properly.

 Thanks for the help
You can put everything in a single library. The module names should match to the folder layout: extensions/regex.d // module extensions.regex; extensions/path.d // module extensions.path; extensions/files/package.d // module extensions.files; extensions/files/files_stuff1.d // module extensions.files.files_stuff1; extensions/files/files_stuff2.d // module extensions.files.files_stuff2; Note the particular case of package.d. To have a module with the same name as a folder you name it package.
Mar 18
parent reply alex1974 <alex.leisser gmail.com> writes:
On Saturday, 18 March 2017 at 12:26:35 UTC, Basile B. wrote:
 On Saturday, 18 March 2017 at 11:29:43 UTC, alex1974 wrote:
 [...]
You can put everything in a single library. The module names should match to the folder layout: extensions/regex.d // module extensions.regex; extensions/path.d // module extensions.path; extensions/files/package.d // module extensions.files; extensions/files/files_stuff1.d // module extensions.files.files_stuff1; extensions/files/files_stuff2.d // module extensions.files.files_stuff2; Note the particular case of package.d. To have a module with the same name as a folder you name it package.
Thanks for the answer. This simple layout works, but then all parts will be compiled every time. Is there a way to just compile the "sublibraries" which have changed?
Mar 18
parent reply Mike Parker <aldacron gmail.com> writes:
On Saturday, 18 March 2017 at 12:49:33 UTC, alex1974 wrote:

 This simple layout works, but then all parts will be compiled 
 every time. Is there a way to just compile the "sublibraries" 
 which have changed?
By "compiled every time", if you're talking about when using the library as a dependency, that's not quite true. dub will compile dependencies on the first run, then only in specific scenarios, not every time. It's really not a big deal. Take a look at dlib [1], for example. On big monolithic library and I haven't seen anyone complaining. But if you really want to, take a look at subpackages[2] in the dub docs. [1] https://github.com/gecko0307/dlib [2] https://code.dlang.org/package-format?lang=json#sub-packages
Mar 18
parent alex1974 <alex.leisser gmail.com> writes:
On Saturday, 18 March 2017 at 13:41:12 UTC, Mike Parker wrote:
 On Saturday, 18 March 2017 at 12:49:33 UTC, alex1974 wrote:

 This simple layout works, but then all parts will be compiled 
 every time. Is there a way to just compile the "sublibraries" 
 which have changed?
By "compiled every time", if you're talking about when using the library as a dependency, that's not quite true. dub will compile dependencies on the first run, then only in specific scenarios, not every time. It's really not a big deal. Take a look at dlib [1], for example. On big monolithic library and I haven't seen anyone complaining. But if you really want to, take a look at subpackages[2] in the dub docs. [1] https://github.com/gecko0307/dlib [2] https://code.dlang.org/package-format?lang=json#sub-packages
Actually the compiling is fast. But its confusing, that all unittests from all sublibraries are performed every time. I thought with subpackages I can perform just the test from the part I'm working on. But I can't get the right layout for the subpackages.
Mar 18