OK- i assumed that target was OK, since it was in the makefile. I'll
discuss this with you some more- perhaps this is the time to abstract away
some of this building-things stuff.
--Josh
At 22:23 on 03/28/2002 PST, "Brent Dax" <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] [mailto:[EMAIL PR
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
# Could you be specific? I was careful to do things identically to
# Configure.pl (because we lack any common code I can use right
# now- that's
# another problem we need to solve)
libparrot.a isn't even the right name on Windows, and the target itsel
Could you be specific? I was careful to do things identically to
Configure.pl (because we lack any common code I can use right now- that's
another problem we need to solve)
--Josh
At 22:03 on 03/28/2002 PST, "Brent Dax" <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED]:
> # This should enable w
[EMAIL PROTECTED]:
# This should enable writing tests which call parrot C
# functions directly,
# which could be useful for increasing coverage to things which
# aren't easy to
# call via opcodes.
And it will shatter Windows. Don't even think about committing it.
--Brent Dax <[EMAIL PROTECTED
