WeakRef updated to better support Tango -- and a question

[Jason House]

Sean Kelly Wrote:

> == Quote from Jaaon House (jason.james.house at gmail.com)'s article
> > Lars Ivar Igesund Wrote:
> > > Jason House Wrote:
> > >
> > > > Regardless, adding -lgtango and -lgphobos doesn't solve my linking issues.
> > > > Below is a copy and paste of the complete output.  I also attached my TT
> > > > code that's causing my problem.
> > >
> > > I wasn't suggesting that these were missing, but rather that you got the Phobos version of the runtime. If that is not the case, could you
> please take it to the Tango forum or create a ticket?
> > >
> > > Lars Ivar
> > Given that I must continue using 0.99.4, and the ensuing pain to rebuild and install Tango without the installer, what is the easiest way to
> test this?
> 
> Use any non-template Tango routine and see if you get a linker error
>  when building the app.  

They're sprinkled throughout the 9000+ line code base.  It all worked before I tried using the weak ref stuff.  I also know that -lgtango was required with gdc to compile with gdc.  I added -lgphobos based off of this thread.


> But I'll admit to being a bit surprised that the
> Tango build process is painful.  It amounts to running one script, 
> at least for the base lib.


I'm not set up for building Tango every day.  The code I used to build/install 0.99.4 was purged from my machine.  I can't go to the Tango web site and download 0.99.4 anymore.  I have to go to svn.  That means looking up the svn repository, finding the code, and checking it out.  Then I have to poke around the Tango web site until I find the instructions on building and installing Tango (again, I don't do it every day).  Running the build script is a step in the process, but I know it isn't everything.  The build script creates stuff, but then the proper files have to get moved to the proper locations.  That includes stuff like tracking down which directories gdc uses.

Maybe I'm slow, but that's not a 2 minute task for me.