<div dir="ltr">On Thu, Jul 24, 2008 at 10:25 AM, sleek <<a href="mailto:cslush@gmail.com">cslush@gmail.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Awesome! Nice dsss tip.<br>
<br>
Thanks Jared! :-P<br>
<br>
"Jarrett Billingsley" <<a href="mailto:kb3ctd2@yahoo.com">kb3ctd2@yahoo.com</a>> wrote in message<br>
news:g5ufre$264o$1@digitalmars.com...<br>
> "sleek" <<a href="mailto:cslush@gmail.com">cslush@gmail.com</a>> wrote in message<br>
> news:g5u57t$1i6n$1@digitalmars.com...<br>
>>I discovered this to be user error. I didn't realize that dsss was<br>
>>creating a "dsss_objs" folder. For whatever reason, I couldn't simply do a<br>
>>"dsss build mymodule.d" and have it cleanly create a new instance. I guess<br>
>>I need to do a "dsss clean" before rebuilding. Thanks for the help Jarret<br>
><br>
> Alternatively, you can do "dsss build -full mymodule.d". That forces a<br>
> full rebuild.<br>
><br>
> And it's Jarrett with two Ts.<br>
><br>
</blockquote><div><br>If you change the dsss.conf file, DSSS will detect that and do a full rebuild.<br>But if other things change out from under it (like library versions or sometimes code) then you will need a -full / or clean.<br>
It isn't like SCONS, which keeps an md5 hash of dependencies to detect any changes that might affect a build.<br><br>--bb<br></div></div></div>