Bill Baxter wrote:
> Gregor Richards wrote:
>> This is an aspect of versioning I hadn't considered very thoroughly. This will definitely be subsumed by the library-versioning support DSSS will eventually have, but this is actually a comparably simple subset. I'll have to muddle over it.
>>
>> I have several compilers, but all in different prefixes with their own DSSS'. It's nice to know that DSSS almost works with your setup ;)
>>
>>  - Gregor Richards

Yes, well, my setup is kinda flaky.  It's amazing anything works at all...

> I was having issues with this too.  It seems that despite the nice prefixes dsss uses to keep dmd and gdc versions of things distinct, when you do "dsss net install derelictgl" it just blows away the previous lib and then installs the new one, even if the prefixes are different.
> 
> Also I was trying to get my Luigi lib to build with dsss under gdc, but
> for some reason no matter what I try it wants to link apps with the SDD
> version of luigi instead of the SDG one.  All I should have to make dsss
> use gdc is to change the "profile=" line in etc/rebuild/default, right?
>  (this was on Linux)
> 
> --bb

Maybe DSSS should have a separate concept of compilers to version flags.
 So when you install something, it compiles it for each of the installed
compilers; that way, DMD 1, DMD 2, GDC, DMD+Tango, etc. can all cooperate.

	-- Daniel

Daniel Keep wrote:
> 
> Bill Baxter wrote:
>> Gregor Richards wrote:
>>> This is an aspect of versioning I hadn't considered very thoroughly.
>>> This will definitely be subsumed by the library-versioning support
>>> DSSS will eventually have, but this is actually a comparably simple
>>> subset. I'll have to muddle over it.
>>>
>>> I have several compilers, but all in different prefixes with their own
>>> DSSS'. It's nice to know that DSSS almost works with your setup ;)
>>>
>>>  - Gregor Richards
> 
> Yes, well, my setup is kinda flaky.  It's amazing anything works at all...
> 
>> I was having issues with this too.  It seems that despite the nice
>> prefixes dsss uses to keep dmd and gdc versions of things distinct, when
>> you do "dsss net install derelictgl" it just blows away the previous lib
>> and then installs the new one, even if the prefixes are different.
>>
>> Also I was trying to get my Luigi lib to build with dsss under gdc, but
>> for some reason no matter what I try it wants to link apps with the SDD
>> version of luigi instead of the SDG one.  All I should have to make dsss
>> use gdc is to change the "profile=" line in etc/rebuild/default, right?
>>  (this was on Linux)
>>
>> --bb
> 
> Maybe DSSS should have a separate concept of compilers to version flags.
>  So when you install something, it compiles it for each of the installed
> compilers; that way, DMD 1, DMD 2, GDC, DMD+Tango, etc. can all cooperate.

I figured out what the problem was with dsss.  I had built once using the dmd-posix profile, and those dsss_imports were still lying around. Apparently they don't get re-generated when the profile changes.  YOu have to manually delete them.  Something to watch out for.

--bb

Reply to Gregor,

> DSSS, the D Shared Software System, is a tool to ease the building,
> installation, configuration and acquisition of D software.
> 
> 0.72 and 0.72.1 have been fairly tiny releases. 0.72 just fixed a bug.
> 0.72.1 is tiny in terms of changes, but the one change is big:
> - Now supports D 2.0.
> Note that 2.0 support is not extensively tested (my primary platform
> is GDC), but it did compile some simple tests.
> 
> As per usual, more information and downloads are available at
> http://www.dsource.org/projects/dsss/
> 
> - Gregor Richards
> 

Feature request: can we get some of dimple's functionality added to DSSS?

http://www.shfls.org/w/d/dimple/

BCS wrote:
...
> Feature request: can we get some of dimple's functionality added to DSSS?
> 
> http://www.shfls.org/w/d/dimple/
> 
> 

That would be nice. Bud has a -uses flag which lists for each module what it imports, that should be enough to recreate dimple in a straightforward manner.

Reply to Lutger,

> BCS wrote:
> ...
>> Feature request: can we get some of dimple's functionality added to
>> DSSS?
>> 
>> http://www.shfls.org/w/d/dimple/
>> 
> That would be nice. Bud has a -uses flag which lists for each module
> what it imports, that should be enough to recreate dimple in a
> straightforward manner.
> 

I'm thinking it would be nice if DSSS could generate some sort of build report. 


Ideally this would be a html file that would list things like:
 the build status of every module
 the output from each modules (sorted by some regex rules)
 an import graphs,
 greps of any recompiled source (for coding standard checks)
 the process run time (how long the build took
 the used command lines flags
 the command lines run
 external libs used
 ...

The next step would be a cgi wrapper script that would kick DSSS and then return the status page. (but we needn’t go there yet :)

BCS wrote:
> 
> I'm thinking it would be nice if DSSS could generate some sort of build report.
> 
> Ideally this would be a html file that would list things like:
>  the build status of every module
>  the output from each modules (sorted by some regex rules)
>  an import graphs,
>  greps of any recompiled source (for coding standard checks)
>  the process run time (how long the build took
>  the used command lines flags
>  the command lines run
>  external libs used
>  ...
> 
> The next step would be a cgi wrapper script that would kick DSSS and then return the status page. (but we needn’t go there yet :)
> 

That would be awesome. I mentioned the -uses option because I thought it might be a good way to get the same thing with less work for Gregor.

Reply to Gregor,

> DSSS, the D Shared Software System, is a tool to ease the building,
> installation, configuration and acquisition of D software.
> 
> 0.72 and 0.72.1 have been fairly tiny releases. 0.72 just fixed a bug.
> 0.72.1 is tiny in terms of changes, but the one change is big:
> - Now supports D 2.0.
> Note that 2.0 support is not extensively tested (my primary platform
> is GDC), but it did compile some simple tests.
> 
> As per usual, more information and downloads are available at
> http://www.dsource.org/projects/dsss/
> 
> - Gregor Richards

when is the scripting/output capture stuff coming out? weeks? months? minutes?

I ask because I'm hoping to convert a project of mine to use DSSS but I don't want to unless I can get some additional processing stuff at the same time.

Another issue/question: Can DSSS be set up to consider a particular file as a library? I ask because the project in consideration has a build time of about 3 sec for all but one file that has a build time of more like 30 sec. (it uses lots of templates) I want to do full rebuilds every time, but that is not going to be practical for that one file. What I'd like to do is run a full rebuild of the whole project and do a partial rebuild of only that part.

BCS wrote:
> Reply to Gregor,
> 
>> DSSS, the D Shared Software System, is a tool to ease the building,
>> installation, configuration and acquisition of D software.
>>
>> 0.72 and 0.72.1 have been fairly tiny releases. 0.72 just fixed a bug.
>> 0.72.1 is tiny in terms of changes, but the one change is big:
>> - Now supports D 2.0.
>> Note that 2.0 support is not extensively tested (my primary platform
>> is GDC), but it did compile some simple tests.
>>
>> As per usual, more information and downloads are available at
>> http://www.dsource.org/projects/dsss/
>>
>> - Gregor Richards
> 
> when is the scripting/output capture stuff coming out? weeks? months? minutes?

The next release should have a midbuild hook command, which will allow you to capture build output, unless I get hung up on stupid stuff. It will also lay the framework for scripting support, though it'll be a release or two before any of that appears. I can't really give good timelines, but somewhere between "weeks" and "months" is probably right.

> 
> I ask because I'm hoping to convert a project of mine to use DSSS but I don't want to unless I can get some additional processing stuff at the same time.
> 
> Another issue/question: Can DSSS be set up to consider a particular file as a library? I ask because the project in consideration has a build time of about 3 sec for all but one file that has a build time of more like 30 sec. (it uses lots of templates) I want to do full rebuilds every time, but that is not going to be practical for that one file. What I'd like to do is run a full rebuild of the whole project and do a partial rebuild of only that part.
> 
> 

Sure. Just like making a package a library, except use a module as the section header:

[foo/a.d]
type=library

 - Gregor Richards

Reply to Gregor,

> BCS wrote:
> 
>> Reply to Gregor,
>> 
>>> DSSS, the D Shared Software System, is a tool to ease the building,
>>> installation, configuration and acquisition of D software.
>>> 
>>> 0.72 and 0.72.1 have been fairly tiny releases. 0.72 just fixed a
>>> bug.
>>> 0.72.1 is tiny in terms of changes, but the one change is big:
>>> - Now supports D 2.0.
>>> Note that 2.0 support is not extensively tested (my primary platform
>>> is GDC), but it did compile some simple tests.
>>> As per usual, more information and downloads are available at
>>> http://www.dsource.org/projects/dsss/
>>> 
>>> - Gregor Richards
>>> 
>> when is the scripting/output capture stuff coming out? weeks? months?
>> minutes?
>> 
> The next release should have a midbuild hook command, which will allow
> you to capture build output, unless I get hung up on stupid stuff. It
> will also lay the framework for scripting support, though it'll be a
> release or two before any of that appears. I can't really give good
> timelines, but somewhere between "weeks" and "months" is probably
> right.
> 
>> I ask because I'm hoping to convert a project of mine to use DSSS but
>> I don't want to unless I can get some additional processing stuff at
>> the same time.
>> 
>> Another issue/question: Can DSSS be set up to consider a particular
>> file as a library? I ask because the project in consideration has a
>> build time of about 3 sec for all but one file that has a build time
>> of more like 30 sec. (it uses lots of templates) I want to do full
>> rebuilds every time, but that is not going to be practical for that
>> one file. What I'd like to do is run a full rebuild of the whole
>> project and do a partial rebuild of only that part.
>> 
> Sure. Just like making a package a library, except use a module as the
> section header:
> 
> [foo/a.d]
> type=library
> - Gregor Richards
> 

so if I want to build main.d, b.d and foo/b.d in one thing but build foo/a.d in another go (assuming that main.d imports everything), that will work?

Something like this:

[main.d]

[foo/a.d]
type=library