D2 port of xfBuild (alpha version)

[torhu]

On 30.11.2011 08:15, Jacob Carlborg wrote:
> On 2011-11-29 22:14, torhu wrote:
>>  On 29.11.2011 13:20, Jacob Carlborg wrote:
>>>  On 2011-11-29 12:00, Andrej Mitrovic wrote:
>>>>  FWIW a couple of bugs from the old issue tracker were fixed in the new
>>>>  fork. Bugs were reported here:
>>>>  https://bitbucket.org/h3r3tic/xfbuild/issue/16/xfbuild-crashes-if-full-path-to-deps-objs
>>>>
>>>>  https://bitbucket.org/h3r3tic/xfbuild/issue/17/xfbuild-crashes-optlink-on-windows-if-o
>>>>
>>>>
>>>>  There was also a multithreaded bug that manifested itself on Windows
>>>>  where printing to the console would be interleaved and left the
>>>>  message scrambled. This is now fixed.
>>>>
>>>>  Also, the +xpath option was added, first discussed here:
>>>>  https://bitbucket.org/h3r3tic/xfbuild/issue/1/add-a-xpath-option
>>>>
>>>>  I'll have to look into the whole template instantiation "fiasco" and
>>>>  see where we are at that and if it can be resolved. Stay tuned.. :)
>>>>
>>>>  https://github.com/AndrejMitrovic/xfbuild
>>>
>>>  Walter mentioned something that if the "-lib" flag is used it will
>>>  output templates to all object files. If that was what you were
>>>  referring to.
>>>
>>
>>  The -lib flag leads to bloated executables. Maybe the linker doesn't get
>>  rid of the duplicates, I don't know.
>
> That may be so, but at least the application works, if Walter is correct
> about the -lib flag. He has also said he doesn't want to add a flag that
> does what's necessary with the templates.
>

Maybe this is about something else than I was thinking of.  I was 
thinking of the linker errors you will get if you do partial rebuilds. 
Missing symbols for struct initializers and things like that.  And 
templates too, I guess.  Can't remember the details anymore.  But the 
-lib flags wouldn't help with that anyway.