<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 17, 2013 at 11:11 PM, Paul Bone <span dir="ltr"><<a href="mailto:paul@bone.id.au" target="_blank">paul@bone.id.au</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Wed, Apr 17, 2013 at 10:57:58PM +1000, Julien Fischer wrote:<br>
> On Wed, Apr 17, 2013 at 10:53 PM, Paul Bone <<a href="mailto:paul@bone.id.au">paul@bone.id.au</a>> wrote:<br>
><br>
> ><br>
> > > You cannot have Mercury programs in that directory. There's no way<br>
> > > it could be compiled with the source distribution. The contents of the<br>
> > util<br>
> > > directory are the first thing that is built (i.e. before the standard<br>
> > > library, which<br>
> > > we we would need to link any Mercury program against).<br>
> ><br>
> > I made it work by altering the way things are built in the main Makefile,<br>
> > This can still build the C programs in util before the runtime, but build<br>
> > the Mercury programs in util (just mfilterjavac) after the runtime and<br>
> > standard library.<br>
><br>
><br>
> Is there any reason that it can't go into a separate directory? I don't<br>
> really<br>
> like the idea of the workflow you're getting make to do during the build<br>
> there -- it's kind of non-obvious.<br>
<br>
</div></div>I suppose we could create a new directory called util_mercury or similar.<br></blockquote><div><br></div><div>You could just call it mfilterjavac.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Can we take this to Google Talk either now or tomorrow.</blockquote><div><br></div><div>Sure, I'll chat to you tomorrow.</div><div><br></div><div>Cheers,</div><div>Julien.</div><div><br></div><div><br></div><div> </div>
</div></div></div>