On Mon, 2011-08-22 at 03:46 -0600, Tor Lillqvist wrote:
I wonder if we should just move the oowintool code into configure.in?
Sure, oowintool is Perl and configure.in is shell, but oowintool isn't
that extremely perlish Perl, it would be relatively simple to
implement its logic in shell code instead.
Cue language war ;-) personally I'd hate that, and having the tool
standalone perhaps helps some quick debugging without re-autogenning
etc. And of course truly-system-independent-non-bash shell is
susbtantially uglier than perl but ... win32 is your world of course :-)
ATB,
Michael.
--
michael.meeks@novell.com <><, Pseudo Engineer, itinerant idiot
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.