dynoplibs in core or no?
Christoph Otto (Excell Data Corporation)
a-chotto at microsoft.com
Tue Jun 1 17:19:50 UTC 2010
> -----Original Message-----
> From: parrot-dev-bounces at lists.parrot.org [mailto:parrot-dev-
> bounces at lists.parrot.org] On Behalf Of Will Coleda
> Sent: Tuesday, June 01, 2010 09:39
> To: parrot-dev at lists.parrot.org
> Subject: dynoplibs in core or no?
> We've had some ping pong'ing code of late regarding the dynop
> libraries as they've been moved in and out of 'make corevm'
> If so, we should actually test all of them as part of core, and not
> just the ones that happen to be in 'corevm' after ops massacre.
> If not, we should not build them as part of core, and we'll need to
> examine the various tests that are failing as part of 'make coretest'.
> Will "Coke" Coleda
Part of the reason they were taken out of coretest was because opsc (and therefore nqp) were required to build them. If we want be able to build them without building nqp (i.e. without adding nqp to corevm/coretest), the best approach would probably be to check the generated dynops C files and headers in to svn.
More information about the parrot-dev