Issue 85324 - 'gperf' needed to build modules 'writerfilter' and 'oox'
Summary: 'gperf' needed to build modules 'writerfilter' and 'oox'
Status: CLOSED FIXED
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: 680
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Martin Hollmichel
QA Contact: issues@tools
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-17 11:33 UTC by rt
Modified: 2013-08-07 15:34 UTC (History)
7 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description rt 2008-01-17 11:33:25 UTC
Follow-up to issue 85318
Beginning with milestone m243 on SRC680 'gperf' is needed to build. There are
two options:
1) make it a prerequisite. If so, that has to be documented at tools.openoffice.org
2) introduce a new module 'gperf'. In that case besides the module itself we
need an alias, changes for configure, and dependencies in writerfilter's and
oox's build.lst files.

Personally, I'd prefer option 1. Especially as on linux and macosx we already
have gperf.
Comment 1 clippka 2008-01-17 12:46:35 UTC
I discussed the options with MH a long time ago before he started the legal
review and we decided to go for option 2.

I put the module gperf for you on my tausch directory. You volunteered to add it
to cvs. Let me know if you have any problems with it.
Comment 2 rene 2008-01-17 13:09:28 UTC
cl: I don't see why we need a gperf module at all. It's build time only.
The Linux distris have gperf, Mac OS X has it too with Xcode cloph says and iirc
cygwin has, too. We don't ship ant for example either...
Comment 3 rt 2008-01-17 13:10:44 UTC
MH today told me he dislikes having gperf as module and 'veto'ed against
committing that module. Martin, cold you please clarify your point of view?

Even if we took gperf as own module there would be some work for you to do,
Christian. Ivo could do the build.lst changes, but that configure stuff would be
yours, I think.
Comment 4 rene 2008-01-17 13:14:56 UTC
rt: if we decide to just rely on external gperf, ther's nothing do to for
configure afais. The check is already there (I committed it longer ago myself:
)http://bonsai.go-oo.org/cvsview2.cgi?command=DIFF&subdir=tools%2Fconfig_office&file=configure.in&rev1=1.237&rev2=1.238&whitespace_mode=show&diff_mode=context
Comment 5 rt 2008-01-17 14:02:24 UTC
Agreement: no module gperf, take it from system / make it a prerequisite instead.

For SO Hamburg build environment I put a gperf binary for solaris and windows
into the common build environment. CL, please document the need for gperf on
tools.openoffice.org . 
Reducing priority.
Comment 7 quetschke 2008-02-05 03:57:04 UTC
I just stumbled over the new build requirement gperf.

The documentation for the windows build in
<http://wiki.services.openoffice.org/wiki/Windows#Extra_requirements>
has several problems.

- It is in the "Using ooo-build" section, but it should be mentioned in the
  "Using vanilla source" section.

- It should not be on that page at all, but should go into:
  <http://tools.openoffice.org/dev_docs/build_windows_tcsh.html>

Also, why is the download of a native w32 gperf.exe requested? gperf is
available as a cygwin package. Mixing native and cygwin tools in the
W32-{ba,tc}sh build is asking for trouble.

I am trying a build with the cygwin gperf right now.
Comment 8 quetschke 2008-02-05 18:36:45 UTC
m245 builds fine with the gperf from the cygwin package.
Comment 9 rene 2010-06-22 16:26:59 UTC
looks liek an obsolete issue, no? we have gperf needed since long..
Comment 10 rt 2010-11-05 09:54:40 UTC
closing