digitalmars.D - simplistic package/build tool
- Martin Nowak (20/20) Jul 14 2011 Because the discussion is rising up, I just added some help/information ...
- Trass3r (1/3) Jul 14 2011 dmd, not D! ;)
- David Nadlinger (3/6) Jul 14 2011 And only for smaller projects.
- Graham Fawcett (4/13) Jul 15 2011 Can you clarify why larger projects are better suited to partial rebuild...
- Nick Sabalausky (6/17) Jul 15 2011 Bigger projects can still take awhile to build. It takes me about 1-2
- Martin Nowak (5/8) Jul 14 2011 Well in D the semantics of a module are independent of where it is
- Andrew Wiley (7/11) Jul 14 2011 Yes, so?
- Andrej Mitrovic (3/3) Jul 14 2011 Until DMD eats up so much memory it starts to crawl down and become
Because the discussion is rising up, I just added some help/information = to = a small tool I wrote some month ago. It's raison d'=C3=AAtre was the ability to develop a larger project out = of = smaller libraries. It can: - compactly specify build targets - install packages with imports/documentation - link dependencies It can't: - build import graphs and do partial rebuilds (waste of time with D) - compile other languages - do net installs It can't yet: - version config settings by platform - do pre/post-build invokations - work with any other compiler but dmd2 It case you might find this useful: https://github.com/dawgfoto/dpk
Jul 14 2011
It can't: - build import graphs and do partial rebuilds (waste of time with D)dmd, not D! ;)
Jul 14 2011
On 7/15/11 12:29 AM, Trass3r wrote:And only for smaller projects. DavidIt can't: - build import graphs and do partial rebuilds (waste of time with D)dmd, not D! ;)
Jul 14 2011
On Fri, 15 Jul 2011 00:31:39 +0200, David Nadlinger wrote:On 7/15/11 12:29 AM, Trass3r wrote:Can you clarify why larger projects are better suited to partial rebuilds? Thanks, GrahamAnd only for smaller projects. DavidIt can't: - build import graphs and do partial rebuilds (waste of time with D)dmd, not D! ;)
Jul 15 2011
"Graham Fawcett" <fawcett uwindsor.ca> wrote in message news:ivpgt6$28l3$5 digitalmars.com...On Fri, 15 Jul 2011 00:31:39 +0200, David Nadlinger wrote:Bigger projects can still take awhile to build. It takes me about 1-2 minutes to build DDMD, which is kind of annoying (beats the shit out of compiling GCC though!). Although, I don't actually know whether or not partial rebuilds would actually improve that.On 7/15/11 12:29 AM, Trass3r wrote:Can you clarify why larger projects are better suited to partial rebuilds?And only for smaller projects. DavidIt can't: - build import graphs and do partial rebuilds (waste of time with D)dmd, not D! ;)
Jul 15 2011
Well in D the semantics of a module are independent of where it is imported from. So you can parse/analyze a module once and reuse that information, while with single object builds you'll have to redo this work for each import. On Fri, 15 Jul 2011 00:29:02 +0200, Trass3r <un known.com> wrote:It can't: - build import graphs and do partial rebuilds (waste of time with D)dmd, not D! ;)
Jul 14 2011
On Thu, Jul 14, 2011 at 5:06 PM, Martin Nowak <dawg dawgfoto.de> wrote:Well in D the semantics of a module are independent of where it is imported from. So you can parse/analyze a module once and reuse that information, while with single object builds you'll have to redo this work for each import.Yes, so? If I remember correctly, there's an option to make DMD compile multiple files at once and emit separate object files (although gdc doesn't have this, and I think this feature would be most useful for gdc), and the D frontend is so fast that no one really cares how long it takes to parse the files a few times. Better yet, parallelize the build.
Jul 14 2011
Until DMD eats up so much memory it starts to crawl down and become slow, at which point single object builds are much faster. They are on my system at least.
Jul 14 2011