While I haven't developed d1 in ages, it's roughly how I experimented with it back in the day. I actually don't understand why you hate it so much or where you see complication. What's "the correct place" mean to you? It's all a matter of the dmd.conf file, which is easy to setup to match any configuration.
Shrug. I'm a huge fan of test in place _then_ install. But do whatever works for you. I'm not trying to impose anything on anyone, just showing how I do it and how easy it is. On 5/30/2011 5:53 PM, Don Clugston wrote: > I still have absolutely no idea why you've set up the tester in such a > complicated way with all these hard-coded paths -- and it doesn't > actually work if you also develop the D1 compiler. > If you simply copy the build result (dmd.exe, or phobos.lib) into the > correct place in your dmd directory, you can just run 'dmd', no need > to mess with all this nonsense about putting your dmd.conf into the > git directory, which does not work if you also test D1. In fact, > sticking *anything* in any of the git directories won't work. > Doing it the way you've done it, is pretty useless for anything except > running the test suite. > > > 2011/5/30 Brad Roberts <[email protected]>: >> On 5/30/2011 12:56 PM, Robert Clipsham wrote: >>> On 30 May 2011 09:21, Walter Bright <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> On 5/29/2011 1:53 PM, Robert Clipsham wrote: >>> >>> >>> ..... >>> >>> ## Running the test suite >>> >>> I actually don't know how to do this, but some instructions should >>> go here. Also take a look at >>> http://github.github.com/github-flavored-markdown/ for information >>> on formatting in this file. >>> ---- >>> >>> I could clean this up and make a pull request if you're interested? >>> ;) >>> >>> >>> Sure! >>> >>> >>> I've just spent the past 10 minutes trying to figure out how to run the >>> test suite so I can add instructions/make a pull >>> request and can't manage it... It's no wonder it's not getting run! >>> >>> I can get a range of different errors, I can't seem to manage to get >>> dmd.conf set up correctly to remove all errors >>> though. Perhaps it would be a good idea to include the relevant dmd.conf in >>> the tests/ directory? >>> >> >> Lemee make this simple.. here's a simple makefile and dmd.conf file that >> 'just work'. >> >> The make file are more complicated than the minimal necessary because they >> have a bunch of targets that I use while >> developing from time to time. The default target, however, is enough to >> clone, build, and test all three packages. >> >> >> _______________________________________________ >> dmd-internals mailing list >> [email protected] >> http://lists.puremagic.com/mailman/listinfo/dmd-internals >> > _______________________________________________ > dmd-internals mailing list > [email protected] > http://lists.puremagic.com/mailman/listinfo/dmd-internals _______________________________________________ dmd-internals mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/dmd-internals
