|Keep It Simple, Stupid|
Re^3: Where should (or could) a distribution override HARNESS_OPTIONS?by afoken (Monsignor)
|on Nov 23, 2012 at 05:30 UTC||Need Help??|
Inline::CPP generates within an _Inline directory a new subdirectory for each build's files.
What is a "build" in this context? I.e. do we have one subdirectory per invokation of a test script, one subdirectory per test script, or one per Inline::CPP version? How are the names of the subdirectories calculated (what are the input parameters for the function that returns the subdirectory name)?
Idea behind the last question: two test scripts, both use a common module that uses Inline:CPP, subdirectory name depends only on that module. Two gccs fight in the same subdirectory.
(I should really install some Inline::* modules. But it's 6:30 am and it will be a long day at $work. No time for fun ...)
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)