On Thu, 06 May 2010 16:01:49 -0700, Walter Bright wrote:
> Graham Fawcett wrote:
>> Simple and well conceived! I would like this for D please (and am
>> willing to help :)).
>
> Any help in this direction will be most appreciated.
I'm slowly working on a proposal, trying to incorporate the feedb
Hello Graham,
If so, what's the minimum harnessing we can impose upon a subproject
writer, to make their library compilable by an automated tool?
For many cases, there is a zero config solution that will work much of the
time: Compile all files and pack them into a .lib/.a
Until that doesn'
Hi BCS,
On Thu, 13 May 2010 01:53:34 +, BCS wrote:
> Hello Graham,
>
>> If so, what's the minimum harnessing we can impose upon a subproject
>> writer, to make their library compilable by an automated tool?
>
> For many cases, there is a zero config solution that will work much of
> the time
Hello Graham,
(b) derives the list of files by including all *.d files, except those
in directories named 'test' and except those which contain a
main() function.
I'm thinking of how to make this work for the simple publication model of
"Put it all out via HTTP/SVN/CVS/GIT/etc.". Anything tha
Hi BCS,
On Thu, 13 May 2010 17:31:34 +, BCS wrote:
>> (b) derives the list of files by including all *.d files, except those
>> in directories named 'test' and except those which contain a main()
>> function.
>
> I'm thinking of how to make this work for the simple publication model
> of "Pu
Hello Graham,
I was concerned
others might think the lack of a pre-compiled library was too hackish
(though I quite like it!). I think I'll proceed, and come back with
some sample code.
[...]
Thanks to your suggestion, I just discovered 'pragma("lib", ...)'
which does exactly what I wanted, a
Hey again,
On Thu, 13 May 2010 18:26:07 +, Graham Fawcett wrote:
> Hi BCS,
>
> On Thu, 13 May 2010 17:31:34 +, BCS wrote:
>
>>> (b) derives the list of files by including all *.d files, except those
>>> in directories named 'test' and except those which contain a main()
>>> function.
>>
On 5/14/10 22:27, Graham Fawcett wrote:
Hey again,
On Thu, 13 May 2010 18:26:07 +, Graham Fawcett wrote:
Hi BCS,
On Thu, 13 May 2010 17:31:34 +, BCS wrote:
(b) derives the list of files by including all *.d files, except those
in directories named 'test' and except those which conta
Hi Jacob,
On Sat, 15 May 2010 15:28:23 +0200, Jacob Carlborg wrote:
>
> If you already have it written the script in python why do you use a
> shell script as the dependency file?
The dependency file isn't strictly a shell script, though the syntax
looks the same. As you see, each line represen
On Sat, May 15, 2010 at 18:27, Graham Fawcett wrote:
>
> On a side note, I've found that dranges, dstats and dcrypt (all from
> dsource.org) all work with a little bit of shoehorning (though I had
> to patch dcrypt to get it to compile under the latest D2: see
> http://github.com/gmfawcett/d-buil
Hi Philippe,
On Sat, 15 May 2010 23:03:54 +0200, Philippe Sigaud wrote:
> On Sat, May 15, 2010 at 18:27, Graham Fawcett
> wrote:
>
>> On a side note, I've found that dranges, dstats and dcrypt (all from
>> dsource.org) all work with a little bit of shoehorning (though I had to
>> patch dcrypt t
On Sun, May 16, 2010 at 06:13, Graham Fawcett wrote:
>
> 'trunk/dranges' would be fine -- keeping 'trunk' makes good sense for
> a Subversion project. For my purposes, any depth is okay, e.g.
> 'trunk/src/lang/d2/dranges' would also work. The key is that modules
> which belong to the 'dranges' pa
12 matches
Mail list logo
