Hi Matt,
On 06/17/2016 02:23 AM, Matthew Schinkel wrote:
I forgot there are other "out of date" compilers in the compiler
directory. To me, this seems odd. The directory gets messy and I could
see someone using one, not knowing they are using a old version since
it came in a new jallib package. I think only the Kyle provided
compilers should be directly in the compiler directory.
OK, I can agree with this.
If anyone wishes to use a variant, they can easily copy into /compiler/
When the name of the 'extra' executables reflex the destination OS and
compiler version it seems to me that one additional subdirectory of
jallib/compiler/ would be sufficient.
Do you think we should have the variants in for example
/compiler/jalv2_pi_2.4q5/ ? They would be included in the package, and
there would be no question as to what version it is, how old it is, or
what system it is for.
Good idea. An accompanying readme file with info about version and
destination-OS(-version) and how the variant was built or could be
re-built seems appropriate.
But only variants of the current version should be in the distribution
packages, older versions can always be downloaded separately from Github.
Look at \compiler\jalv2osx. I see it is for OSX operating system, but
what version of jalv2 is it? How was it compiled and when? Is it
compatible with current jallib libraries and samples?
I have no OSX here, but looking in the executable I read Jalv24q2. Good
reason to not distribute it any more.
When there is agreement about the directory structure for additional
compiler executables I'll move 'my' variants.
Regards, Rob.
--
*Rob H*amerling - http://www.robh.nl
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/jallib.
For more options, visit https://groups.google.com/d/optout.
