#2004: Where did Configure.pl option '--cxx' go to?
-----------------------+----------------------------------------------------
Reporter: jkeenan | Owner: jkeenan
Type: bug | Status: closed
Priority: normal | Milestone:
Component: configure | Version: 3.0.0
Severity: medium | Resolution: fixed
Keywords: | Lang:
Patch: applied | Platform: all
-----------------------+----------------------------------------------------
Changes (by doughera):
* status: reopened => closed
* resolution: => fixed
Comment:
Replying to [comment:7 jkeenan]:
> Umm, Andy, if you reopened the ticket and deleted the 'fixed'
resolution, then, by definition, you '''are''' pursuing it further. :-)
I didn't, or at least I didn't intend to. Apparently the email-to-ticket
system "helpfully" did that without my knowledge or consent. This time,
I'm going in directly through Trac, and I'll reclose it.
> Re-inserting it as a command-line option, and then making sure it gets
into (first) the Parrot::Configure object and (then) the ''Makefile'',
`%PConfig`, etc. would be relatively easy. But where exactly would it be
'''used''' in the configuration system?
It wouldn't. It would simply be a place to record the C++ compiler that
might be used by a hypothetical future someone embedding or extending
parrot in a project that involved C++ code.
> As the other Andy would say, ''"Patches welcome!"''
(I thought that was my line!) Anyway, I already wrote the patch once --
it was commit c528c234cd400c7fcb7019c8e1270e40913e778b.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/2004#comment:8>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
