On 13/06/15 17:30, Andrei Alexandrescu via Digitalmars-d wrote:
On 6/13/15 1:10 AM, Joseph Rushton Wakeling via Digitalmars-d wrote:
Adding LATEST=2.067.1 to the command indeed allows clean to run, but
then -- joy! -- I can no longer rebuild anything, because the cached
DMD 2.067 is deleted
On 6/13/15 1:10 AM, Joseph Rushton Wakeling via Digitalmars-d wrote:
Adding LATEST=2.067.1 to the command indeed allows clean to run, but
then -- joy! -- I can no longer rebuild anything, because the cached
DMD 2.067 is deleted and I need internet connectivity to get it
back.
I don't think
On 08/06/15 21:53, Joseph Rushton Wakeling via Digitalmars-d wrote:
On 08/06/15 19:06, Joseph Rushton Wakeling via Digitalmars-d wrote:
Well, just for one, I tried building phobos docs a couple of days ago while
disconnected from the internet; the whole thing failed because the clones of
stable
On 08/06/15 19:06, Joseph Rushton Wakeling via Digitalmars-d wrote:
Well, just for one, I tried building phobos docs a couple of days ago while
disconnected from the internet; the whole thing failed because the clones of
stable release repos couldn't be done.
No doubt I'm missing a trick, but
On Monday, 8 June 2015 at 16:27:49 UTC, Andrei Alexandrescu wrote:
I build the docs probably a few dozen times every day. I just
press up arrow to fetch the previous command, and enter. Takes
no perceptible time. What's the problem? -- Andrei
Well, just for one, I tried building phobos docs a
On Monday, 8 June 2015 at 16:48:31 UTC, John Colvin wrote:
with dir structure
.
|- dmd
|- druntime
|- phobos
|- dlang.org
clone phobos, edit
clone druntime, edit
clone dmd, compile
compile druntime,
compile phobos
clone dlang.org, make -f posix.mak
boom, my changes are gone
That shouldn't
On Monday, 8 June 2015 at 18:06:47 UTC, Joseph Rushton Wakeling
wrote:
On Monday, 8 June 2015 at 16:27:49 UTC, Andrei Alexandrescu
wrote:
I build the docs probably a few dozen times every day. I just
press up arrow to fetch the previous command, and enter. Takes
no perceptible time. What's the
On Monday, 8 June 2015 at 19:51:28 UTC, Andrei Alexandrescu wrote:
Yah, you'd need to pass LATEST=2.067.1 in the command line.
Then the build process won't need to connect to the internet to
fetch the latest version.
LATEST detection must go. It makes bisecting impossible.
In general, if we
On 6/8/15 3:05 PM, Vladimir Panteleev wrote:
On Monday, 8 June 2015 at 21:53:07 UTC, Vladimir Panteleev wrote:
On Monday, 8 June 2015 at 19:51:28 UTC, Andrei Alexandrescu wrote:
Yah, you'd need to pass LATEST=2.067.1 in the command line. Then the
build process won't need to connect to the
On Monday, 8 June 2015 at 22:25:41 UTC, Andrei Alexandrescu wrote:
Well I trust you can come up with a well-engineered
improvement. -- Andrei
1. We can just put it in the makefile (or elsewhere in the
repository). New releases need website updates anyway (front
page, changelog...).
On Monday, 8 June 2015 at 22:26:23 UTC, Andrei Alexandrescu wrote:
... and there's the well-engineered improvement right there.
Bravo. -- Andrei
The network activity for the autodetection is still a minor
nuisance.
On 6/8/15 3:31 PM, Andrei Alexandrescu wrote:
On 6/8/15 3:29 PM, Vladimir Panteleev wrote:
On Monday, 8 June 2015 at 22:26:23 UTC, Andrei Alexandrescu wrote:
... and there's the well-engineered improvement right there. Bravo. --
Andrei
The network activity for the autodetection is still a
On 6/8/15 3:29 PM, Vladimir Panteleev wrote:
On Monday, 8 June 2015 at 22:26:23 UTC, Andrei Alexandrescu wrote:
... and there's the well-engineered improvement right there. Bravo. --
Andrei
The network activity for the autodetection is still a minor nuisance.
It can be set in the command
On Monday, 8 June 2015 at 21:53:07 UTC, Vladimir Panteleev wrote:
On Monday, 8 June 2015 at 19:51:28 UTC, Andrei Alexandrescu
wrote:
Yah, you'd need to pass LATEST=2.067.1 in the command line.
Then the build process won't need to connect to the internet
to fetch the latest version.
LATEST
On 6/8/15 2:53 PM, Vladimir Panteleev wrote:
On Monday, 8 June 2015 at 19:51:28 UTC, Andrei Alexandrescu wrote:
Yah, you'd need to pass LATEST=2.067.1 in the command line. Then the
build process won't need to connect to the internet to fetch the
latest version.
LATEST detection must go. It
On Monday, 8 June 2015 at 16:14:30 UTC, Andrei Alexandrescu wrote:
On 6/8/15 4:27 AM, John Colvin wrote:
Is there any non-insane way of changing some documentation in
a module
and checking that any links/xrefs you may have added actually
work?
The dlang.org makefile appears to happily erase
On 2015-06-08 15:34, Steven Schveighoffer wrote:
If you just want to check that a file's content is going to show up, I use:
dmd -D -o- -c std/somemod.d
The output is not styled properly. But the output should have working
links.
What about the custom ddoc macros?
--
/Jacob Carlborg
On 6/8/15 9:36 AM, Meta wrote:
On Monday, 8 June 2015 at 13:34:14 UTC, Steven Schveighoffer wrote:
If you just want to check that a file's content is going to show up, I
use:
dmd -D -o- -c std/somemod.d
The output is not styled properly. But the output should have working
links.
FWIW, I
On 6/8/15 10:07 AM, Jacob Carlborg wrote:
On 2015-06-08 15:34, Steven Schveighoffer wrote:
If you just want to check that a file's content is going to show up, I
use:
dmd -D -o- -c std/somemod.d
The output is not styled properly. But the output should have working
links.
What about the
Is there any non-insane way of changing some documentation in a
module and checking that any links/xrefs you may have added
actually work?
The dlang.org makefile appears to happily erase uncommitted
changes in ../druntime and ../phobos. I'm really struggling for
words to describe how
On 6/8/15 7:27 AM, John Colvin wrote:
Is there any non-insane way of changing some documentation in a module
and checking that any links/xrefs you may have added actually work?
The dlang.org makefile appears to happily erase uncommitted changes in
../druntime and ../phobos. I'm really
On Monday, 8 June 2015 at 11:27:58 UTC, John Colvin wrote:
Is there any non-insane way of changing some documentation in a
module and checking that any links/xrefs you may have added
actually work?
The dlang.org makefile appears to happily erase uncommitted
changes in ../druntime and
On Monday, 8 June 2015 at 13:34:14 UTC, Steven Schveighoffer
wrote:
If you just want to check that a file's content is going to
show up, I use:
dmd -D -o- -c std/somemod.d
The output is not styled properly. But the output should have
working links.
FWIW, I avoid building phobos docs. It's
On Monday, 8 June 2015 at 15:07:11 UTC, Atila Neves wrote:
What's _not_ painful?
Atila
It's painful to get set up, but once you do it's smooth sailing.
It took one small edit to the makefile to allow me to build the
website and the docs on Windows.
On Monday, 8 June 2015 at 13:36:08 UTC, Meta wrote:
On Monday, 8 June 2015 at 13:34:14 UTC, Steven Schveighoffer
wrote:
If you just want to check that a file's content is going to
show up, I use:
dmd -D -o- -c std/somemod.d
The output is not styled properly. But the output should have
On 6/8/15 4:27 AM, John Colvin wrote:
Is there any non-insane way of changing some documentation in a module
and checking that any links/xrefs you may have added actually work?
The dlang.org makefile appears to happily erase uncommitted changes in
../druntime and ../phobos. I'm really
On 6/8/15 8:07 AM, Atila Neves wrote:
On Monday, 8 June 2015 at 13:36:08 UTC, Meta wrote:
On Monday, 8 June 2015 at 13:34:14 UTC, Steven Schveighoffer wrote:
If you just want to check that a file's content is going to show up,
I use:
dmd -D -o- -c std/somemod.d
The output is not styled
On 6/8/15 6:33 AM, anonymous wrote:
Slightly different topic, related to changing documentation without
losing your sanity: When building dlang.org, changes in druntime/phobos
are not properly picked up.
You can try deleting a strategic file like
dlang.org/web/phobos-prerelease/index.html which
28 matches
Mail list logo
