I changed the dsss.conf files in some ways.

dwt-win,dwt-linux,dwt-addons
type=sourcelibrary

This will no more build a static library, and the source are no more copied as .di file. Instead the sources are installed as .d files. On application build, then everything is compiled.

I do this in the hope that it will simplify the setup.

dwt-win install has now a call to curl to download/extract/install the import libraries.

dwt-addons installs now the content of the 'res' folder (images,..) into dsss $LIB_PREFIX/res and dwt-samples has the -J$LIB_PREFIX/res added.

I hope, that in some day, one can download dsss, and do some dsss net install calls to have a complete working dmd/tango/dwt environment.

Please let me know, how it works for you.

Frank Benoit wrote:
> I changed the dsss.conf files in some ways.
> 
> dwt-win,dwt-linux,dwt-addons
> type=sourcelibrary
> 
> This will no more build a static library, and the source are no more copied as .di file. Instead the sources are installed as .d files. On application build, then everything is compiled.
> 
> I do this in the hope that it will simplify the setup.

I think that's a good idea.  At least until DWT settles down more. I was thinking to suggest it myself.

> dwt-win install has now a call to curl to download/extract/install the import libraries.
> 
> dwt-addons installs now the content of the 'res' folder (images,..) into dsss $LIB_PREFIX/res and dwt-samples has the -J$LIB_PREFIX/res added.

Does dwt-win install it's res too?

> I hope, that in some day, one can download dsss, and do some dsss net install calls to have a complete working dmd/tango/dwt environment.
> 
> Please let me know, how it works for you.

I'll let you know if I run into any snags.

--bb

On Thu, 17 Apr 2008 05:19:54 +0900, Bill Baxter wrote:

> Frank Benoit wrote:
>> I changed the dsss.conf files in some ways.
>> 
>> dwt-win,dwt-linux,dwt-addons
>> type=sourcelibrary
>> 
>> This will no more build a static library, and the source are no more copied as .di file. Instead the sources are installed as .d files. On application build, then everything is compiled.
>> 
>> I do this in the hope that it will simplify the setup.
> 
> I think that's a good idea.  At least until DWT settles down more. I was thinking to suggest it myself.
> 
>> dwt-win install has now a call to curl to download/extract/install the import libraries.
>> 
>> dwt-addons installs now the content of the 'res' folder (images,..) into dsss $LIB_PREFIX/res and dwt-samples has the -J$LIB_PREFIX/res added.
> 
> Does dwt-win install it's res too?
> 
>> I hope, that in some day, one can download dsss, and do some dsss net install calls to have a complete working dmd/tango/dwt environment.
>> 
>> Please let me know, how it works for you.
> 
> I'll let you know if I run into any snags.
> 
> --bb

Bill are you getting a slowdown in compile time with this. It takes my computer some time to compile the library, even with oneatatime off. (actually seems longer than before). Frank is thinking of switching it back because of this, but if I'm the only one with this problem I can just compile it to a library myself.

On Sat, 03 May 2008 18:25:46 +0000, Jesse Phillips wrote:

> On Thu, 17 Apr 2008 05:19:54 +0900, Bill Baxter wrote:
> 
>> Frank Benoit wrote:
>>> I changed the dsss.conf files in some ways.
>>> 
>>> dwt-win,dwt-linux,dwt-addons
>>> type=sourcelibrary
>>> 
>>> This will no more build a static library, and the source are no more copied as .di file. Instead the sources are installed as .d files. On application build, then everything is compiled.
>>> 
>>> I do this in the hope that it will simplify the setup.
>> 
>> I think that's a good idea.  At least until DWT settles down more. I was thinking to suggest it myself.
>> 
>>> dwt-win install has now a call to curl to download/extract/install the import libraries.
>>> 
>>> dwt-addons installs now the content of the 'res' folder (images,..) into dsss $LIB_PREFIX/res and dwt-samples has the -J$LIB_PREFIX/res added.
>> 
>> Does dwt-win install it's res too?
>> 
>>> I hope, that in some day, one can download dsss, and do some dsss net install calls to have a complete working dmd/tango/dwt environment.
>>> 
>>> Please let me know, how it works for you.
>> 
>> I'll let you know if I run into any snags.
>> 
>> --bb
> 
> Bill are you getting a slowdown in compile time with this. It takes my computer some time to compile the library, even with oneatatime off. (actually seems longer than before). Frank is thinking of switching it back because of this, but if I'm the only one with this problem I can just compile it to a library myself.


I wonder what the status of dsss is?  dmd 1.029 added a new switch "- ignore" (which was requested by Gregor a couple of months ago).  Does this mean that Gregor will be redisigning a simpler/faster dsss/rebulid that uses dmd verbose (and ditches the dmd frontend)?

Hoping we will see something soon. :)

-JJR

John Reimer schrieb:
> On Sat, 03 May 2008 18:25:46 +0000, Jesse Phillips wrote:
> 
>> On Thu, 17 Apr 2008 05:19:54 +0900, Bill Baxter wrote:
>> Bill are you getting a slowdown in compile time with this. It takes my
>> computer some time to compile the library, even with oneatatime off.
>> (actually seems longer than before). Frank is thinking of switching it
>> back because of this, but if I'm the only one with this problem I can
>> just compile it to a library myself.
> 
> 
> I wonder what the status of dsss is?  dmd 1.029 added a new switch "-
> ignore" (which was requested by Gregor a couple of months ago).  Does this mean that Gregor will be redisigning a simpler/faster dsss/rebulid that uses dmd verbose (and ditches the dmd frontend)?
> 
> Hoping we will see something soon. :)
> 
> -JJR

I did the change to sourcelib to simplify the setup and remove the need to rebuild a lib on dwt update.
I use neither of this. I just add the include path with -I at the dsss commandline.
Probably its better to change back to type=lib, what do you think?

On Sun, 04 May 2008 01:00:25 +0200, Frank Benoit wrote:

> John Reimer schrieb:
>> On Sat, 03 May 2008 18:25:46 +0000, Jesse Phillips wrote:
>> 
>>> On Thu, 17 Apr 2008 05:19:54 +0900, Bill Baxter wrote: Bill are you getting a slowdown in compile time with this. It takes my computer some time to compile the library, even with oneatatime off. (actually seems longer than before). Frank is thinking of switching it back because of this, but if I'm the only one with this problem I can just compile it to a library myself.
>> 
>> 
>> I wonder what the status of dsss is?  dmd 1.029 added a new switch "- ignore" (which was requested by Gregor a couple of months ago).  Does this mean that Gregor will be redisigning a simpler/faster dsss/rebulid that uses dmd verbose (and ditches the dmd frontend)?
>> 
>> Hoping we will see something soon. :)
>> 
>> -JJR
> 
> I did the change to sourcelib to simplify the setup and remove the need
> to rebuild a lib on dwt update.
> I use neither of this. I just add the include path with -I at the dsss
> commandline.
> Probably its better to change back to type=lib, what do you think?


Maybe it would be best to keep it simple and encourage people to just use -I as you do.  It seems that taking more steps to use type=lib or type=sourcelib is one of complicated, error-prone or problematic (because both require pre-build and install phases; this may further require a uninstall phase if dwt users have had a previous version of dwt active with dsss; dsss' lack of versioning makes this even more of a problem).

Oh... and has anybody tried using bud with dwt recently? What kind of speed difference is there (between bud and dsss).  I recall bobef gave this a shot earlier.

We should also give Tango's "jake" a try as well. :)

-JJR

Jesse Phillips wrote:
> On Thu, 17 Apr 2008 05:19:54 +0900, Bill Baxter wrote:
> 
>> Frank Benoit wrote:
>>> I changed the dsss.conf files in some ways.
>>>
>>> dwt-win,dwt-linux,dwt-addons
>>> type=sourcelibrary
>>>
>>> This will no more build a static library, and the source are no more
>>> copied as .di file. Instead the sources are installed as .d files. On
>>> application build, then everything is compiled.
>>>
>>> I do this in the hope that it will simplify the setup.
>> I think that's a good idea.  At least until DWT settles down more. I was
>> thinking to suggest it myself.
>>
>>> dwt-win install has now a call to curl to download/extract/install the
>>> import libraries.
>>>
>>> dwt-addons installs now the content of the 'res' folder (images,..)
>>> into dsss $LIB_PREFIX/res and dwt-samples has the -J$LIB_PREFIX/res
>>> added.
>> Does dwt-win install it's res too?
>>
>>> I hope, that in some day, one can download dsss, and do some dsss net
>>> install calls to have a complete working dmd/tango/dwt environment.
>>>
>>> Please let me know, how it works for you.
>> I'll let you know if I run into any snags.
>>
>> --bb
> 
> Bill are you getting a slowdown in compile time with this. It takes my computer some time to compile the library, even with oneatatime off. (actually seems longer than before). Frank is thinking of switching it back because of this, but if I'm the only one with this problem I can just compile it to a library myself.

With type=sourcelibrary, you're not supposed to be building a dwt library at all.  Or do you mean building some other library?
I didn't notice any particularly large slowdown compiling apps.

--bb

On Sun, 04 May 2008 00:00:14 +0000, John Reimer wrote:

> 
> Maybe it would be best to keep it simple and encourage people to just use -I as you do.  It seems that taking more steps to use type=lib or type=sourcelib is one of complicated, error-prone or problematic (because both require pre-build and install phases; this may further require a uninstall phase if dwt users have had a previous version of dwt active with dsss; dsss' lack of versioning makes this even more of a problem).
> 
> Oh... and has anybody tried using bud with dwt recently? What kind of speed difference is there (between bud and dsss).  I recall bobef gave this a shot earlier.
> 
> We should also give Tango's "jake" a try as well. :)
> 
> -JJR

Small correction: type=sourcelib isn't necessarily complicated nor does it use a pre-build, but does require a dsss install phase.  Like you say Frank, it may just be easier to use the -I flag for now.  But, my original point was that if dsss gets an efficiency and speed increase with it's next update, then we may be able to move back to lib or sourcelib types.  Software/Library version control would also be a good addition to dsss.

-JJR

On Sun, 04 May 2008 19:58:36 +0900, Bill Baxter wrote:

> Jesse Phillips wrote:
>> On Thu, 17 Apr 2008 05:19:54 +0900, Bill Baxter wrote:
>> 
>>> Frank Benoit wrote:
>>>> I changed the dsss.conf files in some ways.
>>>>
>>>> dwt-win,dwt-linux,dwt-addons
>>>> type=sourcelibrary
>>>>
>>>> This will no more build a static library, and the source are no more copied as .di file. Instead the sources are installed as .d files. On application build, then everything is compiled.
>>>>
>>>> I do this in the hope that it will simplify the setup.
>>> I think that's a good idea.  At least until DWT settles down more. I was thinking to suggest it myself.
>>>
>>>> dwt-win install has now a call to curl to download/extract/install the import libraries.
>>>>
>>>> dwt-addons installs now the content of the 'res' folder (images,..) into dsss $LIB_PREFIX/res and dwt-samples has the -J$LIB_PREFIX/res added.
>>> Does dwt-win install it's res too?
>>>
>>>> I hope, that in some day, one can download dsss, and do some dsss net install calls to have a complete working dmd/tango/dwt environment.
>>>>
>>>> Please let me know, how it works for you.
>>> I'll let you know if I run into any snags.
>>>
>>> --bb
>> 
>> Bill are you getting a slowdown in compile time with this. It takes my computer some time to compile the library, even with oneatatime off. (actually seems longer than before). Frank is thinking of switching it back because of this, but if I'm the only one with this problem I can just compile it to a library myself.
> 
> With type=sourcelibrary, you're not supposed to be building a dwt library at all.  Or do you mean building some other library? I didn't notice any particularly large slowdown compiling apps.
> 
> --bb

Yes, but I have to build the pieces of the library I'm using, which would be more than if I just had to link them in. But I agree with John, waiting to see what Gregor Will do with dsss might be good.

I have problems when I use dwt as a source library. When I building a dwt application I quite often get missing .obj files but not if I build dwt as a regular library. So regardless what's decided I'll continue to build dwt as a regular library.