> >> The NetBSD nan patch is integrated; thanks again (I'm sure I sent this
> >> in a long time ago :-).
> >
> > Not sure when ( almost before my time! )

My mistake, I think I closed the SF bug here (mostly due to being 'old' and see 
if anyone would notice):

https://sourceforge.net/tracker/index.php?func=detail&aid=1891884&group_id=83870&atid=570954

> Sorry, I am confused. It is in my local tree as a patch that I rebase,
> and hence in the tarball I generated.

Can you upload that to GitHub, repost the patch (or find a URL reference for 
it) please?

Probably to late for inclusion in 1.4

Some ideas to on how to get it to work for different compilers/platforms:

http://stackoverflow.com/questions/1923837/how-to-use-nan-and-inf-in-c
http://tdistler.com/2011/03/24/how-to-define-nan-not-a-number-on-windows

> > I'd like to put the XML help in the source generation, but not
> > actually use it in a build.... but how (given the Makefile has an
> > include statement) ?
>
> I'm not sure what to do, but I wonder if making the xsltproc part of the
> build non-optional would help. gtk doc tools and xsltproc are pretty
> normal on any machine beefy enough to run viking, I would think.

Yes I've now given up in trying to avoid it.

So now I've found Windows builds of xsltproc (and libxml2) so I have a complete 
Windows build using wine.

I just need to resolve a nasty 'acquire' thread bug I introduced, but should 
have an updated git master very soon.


                                          
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Viking-devel mailing list
Viking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/viking-devel
Viking home page: http://viking.sf.net/

Reply via email to